A. Stoewer

If I could get some :+1: from the maintainers I would be willing to work on this feature.

I discovered a bug in `packr` while implementing this feature [#211](https://github.com/gobuffalo/packr/issues/211). I'll suspend the development until it get's fixed.

This would help allot, since currently `setUpdatedAt()` is not invoked in some places and therefor update times are sometimes wrong. There is only one problem: If we want to preserve...

Agreed. Maybe we should collect a list of different error types here in this issue discussion?

I am also not quite sure what is meant by multiplexed dimension...

I just looked at the current implementation of our `createSomething()` methods in the back-end. A typical example looks like this: ``` c++ shared_ptr FileHDF5::createBlock(const string &name, const string &type) {...

> Would you then do all the subgroup creation (e.g. for features in Tag or dimensions in DataArray etc) do in the init method? Yes, especially everything that can go...

Some checks can also move to the front end e.g. ``` c++ if (hasBlock(name)) { throw DuplicateName("Block with the given name already exists!"); } ``` This would simplify the implementations...

> Duplication in the case that there are several create methods? No, but each `init` method of an entity that inherits from e.g. `NamedEntity` has to initialize the `name` and...

@gicmo Currently the C4251 warning only appears inside the HDF5 header H5Exception.h. Is there really something we can do about this?