metaCall

Hi guys, in the last few days I came across a project called MetaCall It aims to allow different programming languages to interoperate. I am not sure of the technical details, but this is similar to efforts such as nimpy, nimjl and genny. Implementing a Nim

Treat memory allocation as effect?

It should be possible to put it behind an "experimental flag" (presuming I understand the basics of the effect system correctly? ;) ). Hmmm, I'd like to try this out but probably have to put if off until after the local holidays.

Preview of coming attractions?

> That's pretty much --gc:regions. We could revive this mode but I remain > unconvinced, cross-region pointers are quite some effort to detect -- either > dynamically or statically. Those are great points. Even writing out my example above I started questioning how you'd transfer between memory

Preview of coming attractions?

You'll be surprised to learn that already exists in some capacity, can read about it [here](https://nim-lang.org/docs/manual_experimental.html#package-level-objects)

Question about memory management with bindings

Thanks a lot. It is a clearer to me now.

Black Friday/Cyber Monday

Here's a BFCM deal to end all BFCM deals - Unique Logo Designs Here's a super Black Friday present on your business - Get a 70% cut price on all Custom Logo Packages plans. Expire Date : 01-30-2022

Preview of coming attractions?

@Araq, is incremental compilation coming in nim 1.8? If so, do you guys have a (month that you) target for the 1.8 release?

Preview of coming attractions?

// I don't personally mind forward declarations and the lack of cyclic imports but we'll get a solution for this too. // Eagerly waiting for this. I request your attention to D's "package" scope. It will be a good idea. If we declare a type with package level scope, the entire project can see th

Question about memory management with bindings

oof, yes, in my example, `bar prods[5]` does a copy, which leads to a double free, which explains these demons flying out of my nose

dot-like operations and calls

Interesting, I didn't see the [RFC](https://github.com/nim-lang/RFCs/issues/341) before. The `.?()` operator would indeed solve my problem. By the way: I tried the workaround with the `()` operator, but I ran into the problem that I cannot differentiate between a function call `option.?foo()` o

dot-like operations and calls

The dot like operator RFC included a proposal for a `.?()` operator too, which I think would be helpful for this case. Don't think it has been implemented.