Email or username:

Password:

Forgot your password?
5 comments
Niki Tonsky

@dotfox it’s the perfect example. The feature is widely adopted among other PLs. It’s obviously good and desirable. It will harm no one. Implementation is probably 30 minutes. Yet “Clojure has its ways”

Kirill Chernyshov

@nikitonsky your not yet released edn reader will likely break after adding such separators. Why are you saying "harm no one"?

Niki Tonsky replied to Kirill

@dotfox what do you mean? Multiple languages with 15+ year history make the change and it’s been fine so far? EDN is also not set in stone: they’ve added tagged literals, namespaced maps, duplicate key check, ##Inf recently. So there’re multiple precedents. It's been fine so far?

Niki Tonsky replied to Niki

@dotfox this change doesn’t even have to go into EDN, it could just be an addition to LispReader. And, as I said, implementation-wise it’s a trivial change

Kirill Chernyshov replied to Niki

@nikitonsky I was about to reply that none of those changes break the reader in unusual way when older version of clojure is used. like reader of any version of clojure prior to 1.10 will not read ##Inf as something valid, exception will be thrown. Unlike 42_000 that can be read as 42 followed by a symbol _000.

But I forgot that underscore does not stop number reading in any version of clojure. So I don't know any technical difficulties in adding separators for number literals.

Go Up