Saverio Miroddi

If you're completely sure that writing this code won't case the executable to panic (which is undesirable, even for broken code) due to pointers undefined behavior, then that's a solution...

> We can start writing the thread-related tests and I guess we'll find out then. But does this mean your mutex lock feature will be blocked? I will check it!

I've changed the title and description, since the race condition is not related to the test environment.

I think `modulo` and `quo` should not be implemented would conflict with Goby's policy of no duplicate methods - @st0012 ?

> We shouldn't support Ruby's super keyword. But we can Can you elaborate a bit on this one? Without `super()`, how do inherited methods invoke the ancestor, in particular, `initialize()`?...

So, the term exact is [method overriding](https://en.wikipedia.org/wiki/Method_overriding). I don't think specific support for module overriding initialize() should be added. The reason is that modules are used for composition; such override...

Ah! I see. Adding doesn't hurt :smile: :+1: I think modules overriding should be taken into account as well (eg. the case where `Member#to_xml` is defined in another module, and...

There is a very interesting discussion in the related [Golang GitHub issue](https://github.com/golang/go/issues/20859).

This is an interesting idea, and somewhat audacious, but the consequences need to be extremely well thought out. First, eliminating `==` implicitly eliminates also other arithmetic operators (`>=`, `

> protect won't be support. can you elaborate a bit on the `private` Goby visibility? will it have the exact same specification as Ruby? using the exact same specification would,...