true, false are displayed as "true", "false" instead of TRUE, FALSE

[armenic]

I tried my best to locate the bug, but could not :(.

To reproduce:

$ cargo run
> true
[1] true
> false
[1] false
> c(true, false)
[1]  true false
> c(true, false, "a")
[1]  "true" "false"     "a"
> TRUE
[1] true
> FALSE
[1] false
> c(TRUE, FALSE, "a")
[1]  "true" "false"     "a"
> 

[dgkf]

Yes, you're right! It's an intentional deviation (described in #6) from R. TRUE/FALSE and true/false all map to the same boolean representations.

TRUE/FALSE/NULL is still provided as legacy for the folks that are trying to speedrun carpal tunnel.

No worries though, there's no clear spec that I'm following - just taking liberties where they feel appropriate. If the project grows into anything more substantial I'll take the time to jot down some guiding principles.

[armenic]

Yes, you're right! It's an intentional deviation (described in #6) from R. TRUE/FALSE and true/false all map to the same boolean representations.

TRUE/FALSE/NULL is still provided as legacy for the folks that are trying to speedrun carpal tunnel.

No worries though, there's no clear spec that I'm following - just taking liberties where they feel appropriate. If the project grows into anything more substantial I'll take the time to jot down some guiding principles.

Thanks Doug, it would be great to have guiding principles and a high level architecture diagram or slide. I still mostly feel uncomfortable with the crate, though it feels much familiar now 👍