Szikszai Gusztáv

> To be honest, I still do not know what I am doing wrong here. There is no `new` keyword in Mint, in this example it's parsed as a variable...

After reading this I think the DevTools warning is misleading. The warning only refers to generated selectors and to those only. Let's take this as an example: ``` component Ui.Something...

> there's no way (as far as I can tell) to access the Http response headers when using the built-in Http module. The headers are missing from the `Http.Response` and...

Since we are using Git repositories as packages and don't know if it makes sense to store versions of them separately, I need to think about how and if this...

I agree, it would be great to have a direct comparison - I'll put it on my todo list :slightly_smiling_face: To answer the points you raised: * performance - Mint...

> It seems like these generated arguments should be ones that cannot conflict, perhaps with an index/uuid like `n9208`, or `__0__`, `__1__`, etc.. That would increase the size of the...

> I'd vote for autoprefixed variable names (interpolated ones). I don't understand what you mean by that.

> I meant that the variable names should be prefixed to avoid clashing with already defined (usually single-lettered) variables. If we prefix every variable that the compiler produces it will...

The `lookups` map is populated in the type checking phase: for the `EnumDestructuring` it's here https://github.com/mint-lang/mint/blob/master/src/type_checkers/enum_destructuring.cr#L26 What is missing is that since `EnumDestructuring` can take other things than `TypeVariable` you...

> In the parsing level, the compiler would have to know that it can be a tuple destructuring but only other tuple destructurings can be in it and not other...