Johannes Asal

Any estimation on when this will be available on stable? Using the sparse registry feature is the only available solution for the following issue in Artifactory https://www.jfrog.com/jira/browse/RTFACT-27248 which is currently...

@kornelski We're already using that option in the clients. However, for production use we must not use the upstream repositories but Artifactory remote caches instead. Now the problem is that...

+1. Definitely needed.

This is what I use: ```rust use rune::{ContextError, Module}; use rune::runtime::Object; pub fn env() -> Object { let mut map = Object::new(); std::env::vars().for_each(|(k, v)| { map.insert(k.into(), v.into()); }); map }...

+1

That's also another candidate for documentation, because I couldn't find anything in the book. There's information about type testing during pattern matching, but nothing about type conversions.

I now use an external function, this is an acceptable workaround for me.

That would help a bit I guess. As a C++ programmer I find the shadowing rules irritating enough in Rust, but what makes it worse in Rune is the combination...

There's one thing that confuses me and needs to be clarified for the patch: Even after removing both `get` and `Protocol::INDEX_GET` instance functions from Vec's native module declaration I can...

Ok I understand. Intuitively I would think that neither the integer nor the range indexing should be an internal Vm operation because if there are instance functions in the native...