Jacqueline Firth
Jacqueline Firth
What if instead of making `==` mean numeric equality on numbers, we just made numbers read as exact decimals by default? Then `1 == 1.0` would be true even if...
I'd be fine with that being false, and telling people if they want to mix comparisons of exact and inexact values, they could use this: ```python is_numerically_equal(1, exact_to_inexact(1)) ``` Exactness-insensitive...
I think of it as a type mismatch. Two things of different disjoint types can't be equal, similar to how `some_number == some_string` is _allowed_, but pointless. It's important that...
`=`, `==`, and `equal?` all having slightly different semantics is not a good state of affairs. I think there should only be one symbolic equality operator and it should have...
Do stateful rename transformers that return identifiers with the `'not-free-identifier=?` property set still break expander invariants? Or is it only the `free-identifier=?` behavior of stateful rename transformers that causes problems?
It's strange that the alias is provided from a separate module.
I think the regular `string` function is provided from both `racket` and `racket/base`.
We're trying to improve this state of affairs, correct? ```scheme (define-syntax-parse-rule (set!-multi (x ...) rhs) #:with (tmp ...) (generate-temporaries #'(x ...)) (let-values ([(tmp ...) rhs]) (set! x tmp) ... (void)))...
In the meantime, you can use `sequence->list`.
@sorawee You could only *add* line breaks to comments, and never remove them. So comments that are too long get split, but lots of short comment lines don't get merged....