Phoenix Himself
Phoenix Himself
This can be a part of other breaking design changes that we should batch together to avoid forcing people to update their scripts every single time
This makes no sense @b1ek as there is `?` operator that does just that.
There are unwraps in Amber and these are called `unsafe` (we could rename them to `ignore`). If you need to `unsafe` (or `ignore`) more commands just do this: ``` unsafe...
Actually `ignore` is not the best keyword either. It means that the command will be ignored which is not true. We have to find a better keyword for this.
The appropriate keyword for this use case would be `neverfails` or `infailable`. However I looked up how the keyword `unsafe` is actually used in the Rust ecosystem. Here is the...
@KrosFire do you propose any better idea for this keyword?
Assume sounds good. This issue need to also cover update in the docs and in the plugins. In the compiler if „unsafe” encountered let’s tell user to use „assume” instead...
The community has chosen the `trust` keyword: https://github.com/amber-lang/amber/discussions/333
Yeah.. I've been thinking about this... if this is a good idea to introduce such type. TypeScript has done it because JS enforced it. Aaaand... in any real project you're...
How about we add generics instead. ```ab fn foo(array: [T]) { } ```