Sam Kellett

I'd definitely prefer the UDL over the macro. The macro feels like a significant step backwards considering how cutting edge this library is. Seeing as the macro actually has similar...

> Would you suggest the dyno::literals namespace be dropped in that case? no because if the UDL is defined inside only the `dyno` namespace the user is required to do...

* Ternary operator (it's actually shocking how bad the had version is): https://godbolt.org/g/6bALYs * Self calling lamdba (again, bad is really bad): https://godbolt.org/g/rGhTSX * Initializer lists: https://godbolt.org/g/cvfZxs etc..

can this be a generic fall-through for the hana::to function? like if not specialised (ala mpl::vector/mpl::list) then just pull out all the types. so: ``` static_assert(hana::to(meta::list{}) == hana::tuple_t); static_assert(hana::to(eggs::variant{1}) ==...

@andrew-otiv I'm trying to do the same thing where I have a proto file that I create a `.rs` from using `rust_prost_library` and I want to implement a trait for...

To answer my own question in case anybody else finds this, you can use `rust_prost_transfrom` to add src files and deps to the create produced by `rust_prost_library` https://bazelbuild.github.io/rules_rust/rust_prost.html#rust_prost_transform

Sure, I've created a PR here: https://github.com/bazel-contrib/rules_ruby/pull/228 I just add mathematical to the Gemfile and then I run: ``` bazel run @ruby//:bundle --java_runtime_version=remotejdk_11 -- install ``` Inside `rules_ruby/examples/gem`. It fails...

> This applies both to JRuby and MRI. Which one do you use? I'm using `jruby-9.4.10.0` but am not tied to that if another on works instead.

Ah I see! Thanks for the heads up. What do I put as `.ruby-version` to use MRI?

To answer my question, `3.4.1` worked and I was able to run `bundle -- install` with that matematical extension! Thanks for the help