Calder Coalson

@ahirreddy: Any progress on this?

Nice! Still needs documentation in README though.


But also very low priority.

Did you two get to talk back in November? It would great to be able to arbitrarily specialize resources at deploy time without needing the entire build system (i.e. `--workspace_status_command`).

Same, I think I would lean towards being concise and matching existing Rust names when possible over mood-correctness. So: * `boxed` because `box` is a Rust keyword and `boxed` has...

Hitting this regularly with: * Docker: 18.3.1 * OS: Ubuntu 16.0.4 LTS * Kernel: 4.4.0-109-generic Duplicate issues elsewhere: * https://github.com/docker/for-mac/issues/1396 * https://github.com/kubernetes/kubeadm/issues/738

One small thing that would be nice to fix: `Cache::fetch` returning references limits possible cache implementations (no `RefCell` for internally mutable caches for example).

The compiler [adds an explicit tag](https://github.com/calder/rasn-stack-overflow/blob/4abfb45ccf0770ac9779d3b759713222020daf96/src/generated.rs#L14-L26) to both the type and the field: ```rust #[rasn(choice, tag(explicit(context, 123)))] //

Experimental fix to remove the redundant type tags on the compiler side: https://github.com/librasn/compiler/pull/120. One nice side benefit is that the macro-expanded code for anonymous types gets a lot simpler: https://github.com/calder/rasn-stack-overflow/commit/59882fdb35e5f94821a3805eeb33d61122336229...