Another great DX improvements release, thanks to the contributors !
I start to see some spontaneous interest in Gleam in the Python/C# shop I work in (without me doing propaganda): its a single data point, but it’s something !
show the unmatched values using the syntax the programmer would use in their code
What a great feature. This really bugs me about rust. You often get an error that mentions Error and you have no idea what it is talking about. There are like 5 types called Error in std alone. (I think that is a problem on its own but the original problem would still exist for cross-crate “collisions”). I would be happy if it just always used fully qualified names, but using the appropriate name based on the current scope is an amazing UX.
Hint: Gleam is not an object oriented programming language so
functions are declared separately from types.
Wow, it’s such a common mistake that a hint was added to the language. It’s interesting though, as the user’s intuition must be to write the syntax like that, despite the language using a completely different paradigm.
On the scale of recurring mistakes it’s not one of the most common ones, but it is easy to add a helpful error for, so we do that. Every little bit can help.
I appreciate they don’t assume people will be all in Gleam all day. I’m switching between 3-4 languages daily and sometimes will attempt things which don’t work in the current one. Sometimes it’s “which flavour of start_with/startWith/prefix/… is it?” sometimes other things.
Congrats on the release! I love the focus on developer experience. The if one in particular was something which confused me at first when I first tried gleam, so it’s great to see!
Another great DX improvements release, thanks to the contributors !
I start to see some spontaneous interest in Gleam in the Python/C# shop I work in (without me doing propaganda): its a single data point, but it’s something !
That’s really cool to hear!
What a great feature. This really bugs me about rust. You often get an error that mentions
Errorand you have no idea what it is talking about. There are like 5 types calledErrorinstdalone. (I think that is a problem on its own but the original problem would still exist for cross-crate “collisions”). I would be happy if it just always used fully qualified names, but using the appropriate name based on the current scope is an amazing UX.Wow, it’s such a common mistake that a hint was added to the language. It’s interesting though, as the user’s intuition must be to write the syntax like that, despite the language using a completely different paradigm.
On the scale of recurring mistakes it’s not one of the most common ones, but it is easy to add a helpful error for, so we do that. Every little bit can help.
I appreciate they don’t assume people will be all in Gleam all day. I’m switching between 3-4 languages daily and sometimes will attempt things which don’t work in the current one. Sometimes it’s “which flavour of start_with/startWith/prefix/… is it?” sometimes other things.
Congrats on the release! I love the focus on developer experience. The if one in particular was something which confused me at first when I first tried gleam, so it’s great to see!
Great new features, many thanks for those! Especially the completion of local variables and function arguments.