Ali Mohammad Pur

imo we should keep it, _at least_ the postincr one, and have it evaluate to the previous value, I find myself writing a lot of (the equivalent of) this in...

Also, Swift has custom operators, which makes that removal tolerable for anyone that cares now (https://grep.app/search?q=prefix%20operator%20%5C%2B%5C%2B%5B%5E%2B%3D%2A-%5D&regexp=true&filter[lang][0]=Swift) And as the last part of my argument, I think we can trust the...

> Sure, as a first step how would you feel about making += the default recommended style I think even banning `foo++` used as a statement is okay, I have...

That doesn't have the same semantics in C++, and I didn't really think about the fact that Jakt does not have references. Though imo removing an op that hasn't been...

Match only accepts values as `(expr) =>`, right now only variant names are allowed without parenthesis: ``` function main() { match b'.' { (b';') => 0 else => 1 }...

The error should be more clear at the very least, and the syntax is still fairly experimental (like most of the language :P), so we can leave the issue open...

I'm fairly against pretending that typenames are values, we don't have type-level computations, and we don't have kinds, so `T` wouldn't actually be a "type", it'd have to be magically...

@Sagrel that's not really about function overloading, and your example isn't really overloading on the return type - it's a generic function whose type parameter is inferred from the expected...

We've had some related discussions in #4286, linking that here as a reference.

- `gemini.circumlunar.space` switched to ECDHE+ECDSA a while back, that's WIP - `geminispace.info` should work, but looks like we're rejecting self-signed certs now (cc @msvisser I think you rewrote this part...