Christian Vetter
Christian Vetter
You are correct. I will check with the different API teams using the encoding if they actually have a shared understanding of the units, or if this is up to...
It looks like there are various usecases which require different definitions of the 3rd dimension e.g. there are various choices for how to represent elevation, amongst them: * meters delta...
That makes sense @Alegom . Do you want to open a pull request for that, or do you want to wait for somebody else to do so?
I assume they are still sorted in the normal way (increasing, negative before positive)? In that case we could just convert Ids to be signed and everything should mostly work...
This is due to the generator supporting to deserialize enumerations: Those need to be transmuted. The generator could theoretically skip the useless transmute by checking if target type matches source...
Only in debug mode, release mode optimizes everything away. Similarly the `flatdata_read_bytes` macro is fully optimized to generate code similar to C++ bitfields.
One thing to consider with regards to flatdata and Rust's memory safety guarantees is that Rust requires that the contents of memory mapped flatdata resources does not change as long...
Closing, the version was merged a while ago
Closed this issue, it was accidentally left open for all this time :)
Closing this, as the C++ implementation has been completely rewritten since then