Laurence Morgan

Request for naming suggestions

1

The builtins are pretty undiscoverable at the moment and that's an issue because of the number of builtins that are included with Murex. > The original naming convention borrowed inspiration...

escape builtins should follow the `escape` prefix like list builtins do

1

**Describe the problem:** To make the escape builtins more discoverable, they should follow a similar naming convention to list builtins.

WARNING: change in syntax for `for` in upcoming release: 6.3.x

1

The `for` builtin is switching from parenthesises to curly braces: old syntax: `( ... ; ... ; ... )` new syntax: `{ ... ; ... ; ... }` This is...

**Describe the change:** `IsMethod()` was added to the API long after the escape builtins were written and is a much more accurate way for determining if a builtin is a...

**Describe the bug:** Statements are being executed as an expression when the first parameter is a `=` ``` murex » f == bob cannot EqualTo left Bareword Expression: f ==...

**Describe the bug:** An object of a variable inside an object would return a nested object. eg ``` murex » bob = %{a:1, b:2, c:3} murex » %{hello: $bob} {...

Should `~` error if username not found?

2

**Describe the problem:** The unhappy path for `~` is to produce root path: ``` » ~foobar / ``` This could lead to errors creeping in silently. **Possible ways to implement:**...

Should parenthesis inside array and object creators be parsed as expressions?

1

**Describe the problem:** parenthesis in expressions and statements allow for nested expressions, eg ``` » echo (1+2) 3 ``` but the same doesn't apply within array and object creators. eg...

**Describe the bug:** Nil pointer error merging an object with an array of maps ``` murex » %{} ~> %{bob: [{message: "hello $k"}] } Error in `expr` (0,1): cannot merge...