Allow selecting owned identifier memory representation via regular environment variable about ruma HOT 7 OPEN

I don't think so, but just making sure

from ruma.

Doesn't this require a build.rs?

from ruma.

Yes, is that problematic?

from ruma.

What is the benefit over using cargo features?

from ruma.

Cargo features are additive and can be enabled from any place in the dependency tree. For the owned identifier representation, one specific value must be set (it wouldn't make sense to activate multiple ones).

from ruma.

It can become a compiler error to activate multiple ones. This has potential to make some libraries unusable with each other, but I think in practice all libraries will delegate this decision to the main binary (specially when docs encourage that). I would prefer cargo features for better tooling support and less problems like this, but YMMV.

from ruma.

If it'll become a compiler error, then multiple libraries will become mutually exclusively incompatible with eachother, which is not what we want

from ruma.