Ben Boeckel

It'd probably be worth trying to get all of this rebased on top of master. There have been a number of changes there that need to be accounted for in...

Not sure how easy it'd be for you, but could you get [Derelict](https://github.com/DerelictOrg) any my [bulletml](https://github.com/mathstuf/bulletml) library built and try [mu-cade](https://github.com/mathstuf/abagames-mu-cade)? I'm getting this build rule: ``` ninja command =...

I may not have the most up-to-date code. Will try tomorrow.

FWIW, there's a similar problem in C with `#include ` which CMake might get wrong.

FWIW, you can also bundle the LFS attributes in an `[attr]lfs` as well (we do this to make it easier to manage the attributes files). This pattern also does not...

Thanks! Have you reached out about adopting the crate or republishing under another name (I see you've used your username at least but I'm not sure what that means for...

> This lets you use the original yaml_rust::* namespace. No other references to the fork end up in the code. Alas, all consumers also need to move to use this...

Inferring remote schemas is going to break reproducible builds. It could also break API compatibility easily. I'd rather there be a "here's a schema we committed to the repository" for...

Maybe? I'm not familiar with `diesel`, but it looks like something in the right direction. Is there anything stopping it from being as simple as something like: ```rust let schema...

The reproducible builds thing is just the first that came to my mind. I'm more worried about API stability. SQL schemas may be fine since they're usually only applicable for...