06:12 <anthropy> hey there, I have a strange issue with Sandstorm on Arch (and I think Fedora too but I can reproduce it consistently on my Arch setup now), where I can't create new grains of some larger applications like Wekan. I don't know what's causing it, but I documented it here https://github.com/wekan/wekan/issues/2200 (because they requested me to make a ticket there)

06:46 <anthropy> and also posted it here https://github.com/sandstorm-io/sandstorm/issues/3125 cause it seems more a sandstorm issue than a wekan issue

16:07 <thavlik> Is cap'n proto intended to be convenient to use in-memory?

16:08 <simpson> Like, between threads or actors? It could be used that way, but I don't know whether the C++ library was intended for that.

16:08 <thavlik> I'm working with the rust crates. I keep looking for what should be simple example code and have not found any

16:08 <thavlik> capnproto-rust/examples has the addressbook, but that's not quite what I am looking for I don't think

16:27 <thavlik> Also, I do not seem to be able to use rust 2018 syntax with the code generator. It's still complaining about using ::qualifier instead of crate::qualifier or super::

16:28 <thavlik> [dependencies.capnp] version = "0.9.4"\n edition = "2018" is specified

16:29 <thavlik> i compile with `cargo build` using the build.rs that was shipped with the examples, as well as `RUST_EDITION=2018 capnp compile -orust src/defs.capnp`

16:29 <thavlik> neither yields the appropriate 2018 rust syntax

16:33 <thavlik> I will try with the compiler options. I see the issue on github specifying that

16:34 <thavlik> Kinda confused as to why I have to do this

16:34 <thavlik> Doesn't _everyone_ use 2018 rust by default?

16:34 <thavlik> I've wasted two hours this morning fixing this stupid problem

20:31 <thavlik> Oh my god. capnp rust is so broken

20:33 <isd> thavlik: what's the issue?

20:36 <thavlik_> I installed it with brew prior to realizing it was out of date. I uninstalled that and installed the version from git. Now it's complaining about this:

20:37 <thavlik_> https://pastebin.com/c7Arh1Zy

20:37 <thavlik_> thread 'main' panicked at 'compiling schema: Error { kind: Failed, description: "Error while trying to execute `capnp compile`: Failed: failed to fill whole buffer. Please verify that version 0.5.2 or higher of the capnp executable is installed on your system. See https://capnproto.org/install.html" }', src/libcore/result.rs:1009:5

20:38 <thavlik_> capnp --version is 0.8-dev

20:38 <thavlik_> isd: I am being slightly facetious <3

20:39 <thavlik_> s/facetious/hyperbolic

20:39 <thavlik_> Though I do think forcing people to use build.rs to use the rust 2018 syntax is cumbersome

20:40 <thavlik_> I've spent all morning trying to get it working

21:56 <thavlik> I can't even play with it until this is fixed :/

21:56 <thavlik> Guess I'll file a bug report.

22:13 <thavlik> Does CompilerCommand actually output anything?

22:14 <thavlik> I'm in the build.rs script here. I set the env variable OUT_DIR to an absolute path and capnp generates nothing

22:17 <thavlik> I'm on my debian machine now and can't get the included build.rs examples to output any files to any directoryh

22:24 <thavlik> So let me get this straight - there's no way to specify Rust 2018 without using the build script, and the build script doesn't actually output files?

23:04 <isd> I'm not terribly familiar with the rust implementation myself; have mostly worked with the Go & Haskell ones. Wish I could be of more help