Thomas Schaller

What does `c++ -v` output? On Fedora I get this: ``` Using built-in specs. COLLECT_GCC=c++ COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-redhat-linux Configured with: ../configure --enable-bootstrap --enable-languages=c,c++,fortran,objc,obj-c++,ada,go,lto --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared...

This would be really nice, but I think it becomes tricky once you're dealing with combined flags (`COLOR_ATTACHMENT | DEPTH_ATTACHMENT`). Otherwise I'd already be creating a PR :)

I didn't see the `Debug` implementation. I wouldn't call it straightforward though. The most reasonable implementation is using a string IMO. Would be nice to hear some other opinions.

Is there any reason why this is not being considered? This would be so helpful for actually finding errors in YAML files.

Same issue for me, it seems to be caused by (tagged) enums.

@WaDelma @Xaeroxe Do you think we should add another custom derive?

I think this is a huge usability issue in saveload that should be addressed before stabilizing it.

I think I'm missing some context here, but if you just need mutable access to something from a system, that shouldn't be a problem, you can just use `Write

Oh are you forced to use the `GameState`? Because yes you're not gonna be able to store a non-static reference in `World`. If you cannot get ownership of `ctx` you...

This seems still relevant; I'm thinking that maybe we could solve this by adding a demo.