Based on feedback from this community, I've updated the default syntax for the
fluent package to use ~> and ~~> for function composition. This way, there is
no conflict with the > operator. Here is some example code:
(require fluent)
("hello world" ~> string-split ~~> map string-upcase) ;; '("HELLO" "WORLD")
You can now use (rename-in) to change the syntax if you don't like the defaults:
(require (rename-in fluent (~> >) (~~> >>)))
("hello world" > string-split >> map string-upcase) ;; '("HELLO" "WORLD")
There are also two built-in alternative syntaxes, fluent/short (which uses >
and >>) and fluent/unicode (which uses → and ⇒):
(require fluent/short)
("hello world" > string-split >> map string-upcase) ;; '("HELLO" "WORLD")
(require fluent/unicode)
("hello world" → string-split ⇒ map string-upcase) ;; '("HELLO" "WORLD")
See the README for help entering unicode characters.
Thanks for the feedback and helping me improve this package. I'm not planning
to make any further changes at this stage, so it should be safe to start using
this package if you like.
github: https://github.com/rogerkeays/racket-fluent
package page: https://pkgs.racket-lang.org/package/fluent
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-users/sigid.2715e859bd.20210322130142.GA3098%40papaya.papaya.
