Árpád Goretity 

Hi! > You have omitted that ugly Switch-Case-Stuff because the same can be done with a chain > of Ifs and Elses. Not quite; `switch` isn't in the language because...

Hi! Yes, that's a correct observation. This is a known issue with Sparkling. Since the VM uses reference counting for memory management, circular references currently cause a leak — and...

Yay! An stdlib function seems reasonable.

Just because I know your background: `join` is a less fancy name for `componentsJoinedByString:` :P So, no.

Yup, and strings are very similar to arrays in many other aspects as well... (maybe I should make the `indexof()` standard library function accept arrays too.)

1. Not sure what you mean by "to code", but you can import a module by calling the `require()` function in the standard library. 2. Currently there is no such...

> the syntax gets out of hand rather quickly. Citation needed. Or, I just don't see how specifying the type constraints for an impl counts as "syntax getting out of...

It looks like you are trying to put the trait bounds on the type definition and infer them from there in the `impl` block. That's not great – because, for...

> Why? You can look it up on URLO. That's the entire point that I was making w.r.t. interoperability, and that you have missed, apparently. Edit: [Official API guidelines](https://rust-lang.github.io/api-guidelines/future-proofing.html#data-structures-do-not-duplicate-derived-trait-bounds-c-struct-bounds), [the...

The "other language" also does it with dynamic dispatch. Then so can you. It is **not** the case that dynamic dispatch makes the types go away. In the case of...