Vladimir Vasilyev
Vladimir Vasilyev
### Expected behavior Indexing with path notation evaluates all `any-function!` values. Indexing with `pick` and similar functions doesn't trigger any of them. ### Actual behavior Path notation works as expected...
**Describe the bug** Some natives treat `unset` as truthy: ```red >> if () [1] == 1 >> unless () [1] == none >> any [()] >> all [()] >> not...
**Describe the bug** Red has 3 types of comparison differing by strictness: lax comparison (default), strict comparison and identity comparison. `any-function!` values are always compared by identity, regardless of the...
**Describe the bug** If setting a word to a function follows a pattern other than `: `, such as `: : ` or `set [] `, then compiler does not...
**Describe the bug** Removing a `handle!` value from `parent/state` block in a newly created `face!` makes View unusable. **To reproduce** ```red l: layout [] take l/parent/state ``` After that any...
**Describe the bug** It is generally assumed that comparison between any given values should yield the same result as a comparison between containers that hold such values. This assumption does...
### Expected behavior ```red >> data: "aabbbcccc" == "aabbbcccc" >> move/part data tail data 2 == "bbbccccaa" >> move/part data skip data 7 3 == "ccccbbbaa" >> data: "bbbccccaa" ==...
In View reference docs, some of the face types have tables with descriptions of supported event types and their respective handlers, but some do not: * base * text *...
[Section 6.3.5](https://static.red-lang.org/red-system-specs.html#section-6.3) shows `vprint` as an example of variadic typed function. This function uses `form-type` conversion which was removed from Red/System runtime quite a while ago, so the code needs...
### Expected behavior Either meaningful error message or casting of element(s) to `float!` (once `float!` is supported in `pair!`s of course). ### Actual behavior ```Red >> 123123123123x123123123123 == -2147483648x-2147483648 ```...