Redefine >> macro as >-> in >.el
I created a strangely named Elisp module, >.el, just to appease the CI gods. My gut tells me that this is a desperate idea and fails the smell test. I'm pretty eager to pass the linting phase of my Elisp CI, however, and I can always revert this.
This commit is contained in:
parent
718899c629
commit
75a9a156a0
8 changed files with 53 additions and 26 deletions
|
|
@ -20,7 +20,7 @@
|
|||
(require 'alist)
|
||||
(require 'stack)
|
||||
(require 'struct)
|
||||
(require 'macros)
|
||||
(require '>)
|
||||
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;; Create
|
||||
|
|
@ -47,7 +47,7 @@ The newest bindings eclipse the oldest."
|
|||
"Push a new, empty scope onto XS."
|
||||
(struct-update scope
|
||||
scopes
|
||||
(>> (stack-push (alist-new)))
|
||||
(>-> (stack-push (alist-new)))
|
||||
xs))
|
||||
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
|
|
@ -75,7 +75,7 @@ The newest bindings eclipse the oldest."
|
|||
"Set value, V, at key, K, in XS for the current scope."
|
||||
(struct-update scope
|
||||
scopes
|
||||
(>> (stack-map-top (>> (alist-set k v))))
|
||||
(>-> (stack-map-top (>-> (alist-set k v))))
|
||||
xs))
|
||||
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue