moss heim

I do really think these are important points to pin down though - why prioritize only these messages and not make more aspects of execution control into messages? And why...

> FWIW Julian is correct here. They already are messages. All flow of control structures are messages in SC. There's nothing distinct from messages to be made into messages. I...

Julian wrote: > why you would prefer to make if a keyword, but not +? See the end of this post, I think I've addressed this there. But one reason...

> Messages have no type signature. Not even the implementation of a method in a given class has. ADTs and objects overlap in some of their functionality, but live in...

> But sclang only has objects and no data types. The subclasses of the RawArray generic (String, DoubleArray, etc.) are something of an exception to this, I think.

> But unfortunately that wouldn't work for the Example 2 (LazyEnvir), because we depend on the receiver implementing if in a completely different way: instead of returning something, it wraps...

> The Code of Conduct states that a team of moderators should be contacted in case of a violation of said code, yet it is not clear > > *...

@telephon Interesting, that sounds very much like enforcing a code of conduct to me, which you have just said above you do not believe in. I find your response to...

This is all just incredibly disappointing, and I'm glad I'm no longer involved in this project. Regarding the RFC, for what it's worth I fully support the initiative.

I want to reiterate that my work was plagiarized by a contributor to this project, who also directly attacked myself and other contributors when this was revealed. Assuming that the...