benn/lumiera_documentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

sanity: better not to unwrap Placements automatically

Browse source 
quite sure I never really meant to do that, just, at that time,
it seemed logical to treat Placement as yet another smart-ptr.
But in the light of what crucial entity Placement became meanwhile,
I can't imagine a single case where anyone wants to wrap away a
placement as if it was some shrink-wrap
This commit is contained in:
Fischlurch 2016-01-09 01:55:28 +01:00
parent 6633cb03bd
commit c29af56d1c
2 changed files with 1 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/lib/format-util.hpp
View file

@ -175,7 +175,7 @@ namespace util {
inline string
join (CON&& coll, string const& delim =", ")
{
using Coll = typename lib::meta::Strip<CON>::Type;
using Coll = typename lib::meta::Strip<CON>::TypePlain;
using Val = typename Coll::value_type;
std::function<string(Val const&)> toString = [] (Val const& val) { return util::toString(val); };

13
src/lib/meta/trait.hpp
View file

@ -182,19 +182,6 @@ namespace meta {
}
};
template<typename X, class B>
struct Unwrap<mobject::Placement<X, B> >
{
typedef X Type;
static X&
extract (mobject::Placement<X,B> placement)
{
ASSERT (placement.isValid());
return *placement;
}
};
/** convenience shortcut: unwrapping free function.
* @return reference to the bare element.