Verify interval operator precedence in output #19

New Issue

patrick · 2018-05-02T18:18:39+02:00

patrick commented

2018-05-02 18:18:39 +02:00

When writing 1 + 2..5, this seems to be interpreted as (1 + 2)..5 and not 1 + (2..5), which is what I’d have expected.

I believe that this is inconsistent with anthem’s output, which might incorrectly print (1 + 2)..5) as (1 + 2..5).

When writing `1 + 2..5`, this seems to be interpreted as `(1 + 2)..5` and not `1 + (2..5)`, which is what I’d have expected. I believe that this is inconsistent with anthem’s output, which might incorrectly print `(1 + 2)..5)` as `(1 + 2..5)`.

patrick added this to the anthem 0.1.9 milestone 2018-05-02 18:18:39 +02:00

patrick self-assigned this 2018-05-02 18:18:39 +02:00

patrick added the

bug

label 2018-05-02 18:18:39 +02:00

patrick changed title from ~~Verify interval operator precedence~~ to Verify interval operator precedence in output

2018-05-02 18:18:53 +02:00

patrick commented

2018-05-04 15:52:44 +02:00

Fixed by 1f7f6a02b429ac72bde28418a7ea15465bb0c0e7.

patrick closed this issue

2018-05-04 15:52:44 +02:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: patrick/anthem#19