ollie

How are you building?

My motivation is based on cross compiling, where I might have specified a bunch of rustflags for a target architecture. Currently they are ignored. There are workarounds for this, but...

I'd only considered in-tree config, for the reasons you state. The flags in my config.toml file are: ```toml [target."aarch64-unknown-linux-musl"] linker = "aarch64-unknown-linux-musl-ld" rustflags = ["-C", "target-feature=+crt-static", "-C", "link-arg=-s"] [target."x86_64-unknown-linux-gnu"] linker...

We've done a emergency hack which could act as the basis for a proper PR for this feature. Rational here https://github.com/etlsystems/cargo2nix/pull/3

This might be better as a discussion?

- Builder API: i think we should unify some of the zoo of ops. - Fine grained control over _when_ an op is submitted to the ring - Timer /...

Something which does strike me with this design is the similarity to the existing registries. I strongly suspect these could be unified too, probably by parameterising a Rawbuffer over the...

> > Something which does strike me with this design is the similarity to the existing registries. I strongly suspect these could be unified too, probably by parameterising a Rawbuffer...

> If you didn't provide a straw man proposal for a FixedBuf, is that because you don't know yet or because it's obvious? I would want the BufX I have...

> What would it do to the API if the buffer were made of multiple backing stores though. Doesn't it mean the ref and ref_mut can't be asked to return...