quodlibetor

9 ms·

31.
by quodlibetor 9y ago
It's available online: https://doc.rust-lang.org/book/second-edition/ , a publisher that didn't believe in digital sharing that also agreed to publish it would be a little... surprising.
32.
by quodlibetor 10y ago
That all makes sense, and the immediate return + threads solution you describe sounds like what I was imagining, I just didn't have the context to use the correct parts of the Erlang FFI. I'm glad that there is a pattern for that
33.
by quodlibetor 10y ago
> to write a NIF that could somehow yield back and then be "continued" later would be a royal pain. I know... nothing... about the NIF interface, but the way that I would want this to work wouldn't involve NIF resumption
34.
by quodlibetor 10y ago
Docker is go, and afaik has always been. https://github.com/docker/docker
35.
by quodlibetor 10y ago
Plantuml is (I think) built on top of graphviz. In any case the syntax is extraordinarily similar. This[1] is similar to the first example: @startuml component ripgrep component ignore component globset component grep ripgrep
36.
by quodlibetor 10y ago
Darn, I was hoping that they were created with some custom [plantuml] theme that I could steal, but it seems like they're [manually created] with inkscape. [plantuml]: http://plantuml.com/ [manually created]: view-sour
37.
by quodlibetor 10y ago
For the non-install case, like when you're running a package index, having to eval the dependency specifying is horrible. This is also why wheels (the new python package format) use a static file instead of setup.py. The Python ecosyst
38.
by quodlibetor 10y ago
To make this more concrete, you're suggesting something like [dependencies] hyper = { metapackage = { rust-platform = "2.7" } } I like the general theme of having the platform be just a set of known-compatible vers