Christophe de Dinechin

Hi @tripleo1. Interesting experiment you are trying to do here! Well, it used to work due to a weakness in how g++ was processing weak symbols. You can "patch it"...

> On 11/24/21 12:23 PM, Christophe de Dinechin wrote: > I just chose that one because it was the only one that seemed to work.  I think I read most...

@dumblob, thanks for the insightful remarks. First, please do not reach any conclusion on the design of the language based on any particular commit, in particular right now as I...

> First question - is the `:=` notation just a syntactic sugar for "immutable `is`" (i.e. identical with the very only difference that the identifier can't be "redefined" any more...

> Second question is how do I ensure the function I'm currently implementing is a pure one if `nil` is being automatically propagated breaking the purity? `nil` is not automatically...

> Third question is whether a variable holding an error value is being immediately automatically propagated or first at the place where it's being used (either being written to or...

> Fourth question: could you (dis)approve my understanding that `nil` value fundamentally exists because it's impossible to make a function returning just the type `error` alone without any additional "meaningful...

This is flagged as WIP because in the current incarnation, I have (at least) two problems: * On a very slow network, the setup often ends up with a `unable...

Also notice that in the original post-setup run, I see this: ``` [preflight] Running pre-flight checks [WARNING FileExisting-tc]: tc not found in system path error execution phase preflight: [preflight] Some...

> @c3d, so, we're adding yet another way to run CIs locally, apart from the vagrant one? The question that comes to my mind is why not making the vagrant...