Consider avoiding the build script about hypher HOT 5 CLOSED

I guess you could reference matklad's post on the topic unless you really want to write your own take.

from hypher.

I was definitely going to mention matklad as the inspiration since I originally got the idea from steveklabnik/semver-parser#50, but I think the post you linked to underemphasizes that people should avoid build scripts where possible, and overemphasizes the idea of magic code insertion, where in my experience just generating code into a directory hierarchy in src works well and maybe even better for most of the cases I've encountered (so far I've contributed changes like this to about 5 or 6 projects).

from hypher.

Thanks for the kind words! I'll have a look at this soon.

from hypher.

@djc I see where you're coming from, but it's kind of painful. I just attempted this and the code-generating test doesn't compile because the crate does not build without the generated code. Is there a typical workaround for this? In general, I share the sentiment not to inflict unnecessary bloat on the downstream users, but I'm not sure if the win is that big here, as hypher's build process does not have any dependencies.

from hypher.

I usually commit the generated code in the repo. If you accidentally botch some part of the code generation process such that the generated code doesn't build, I usually just comment out a bunch of stuff to make it work again. In my experience, the code generation code doesn't change very often so it's not a big deal -- IMO it's worth not inflicting the extra compile time on downstream users (even without extra dependencies).

from hypher.