-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change aliases to use rename-out. #18
Conversation
Contracts do not inherit.
I would rather do the renaming in an interface file. In
|
"Fix" vector*->matrix bug in bessjs test suite
Not sure why it says its failing? (λ bkc39 . racket/mechanics) (λ b . aliases) λ cd ..
(λ bkc39 . cs/racket) λ raco pkg update mechanics/
Updating:
mechanics
Uninstalling to prepare re-install of mechanics
Re-installing mechanics
raco setup: version: 6.2.1 [3m]
raco setup: installation name: 6.2.1
raco setup: variants: 3m
raco setup: main collects: /Applications/Racket v6.2.1/collects
raco setup: collects paths:
raco setup: /Users/bkc39/Library/Racket/6.2.1/collects
raco setup: /Applications/Racket v6.2.1/collects
raco setup: main pkgs: /Applications/Racket v6.2.1/share/pkgs
raco setup: pkgs paths:
raco setup: /Applications/Racket v6.2.1/share/pkgs
raco setup: /Users/bkc39/Library/Racket/6.2.1/pkgs
raco setup: links files:
raco setup: /Applications/Racket v6.2.1/share/links.rktd
raco setup: /Users/bkc39/Library/Racket/6.2.1/links.rktd
raco setup: main docs: /Applications/Racket v6.2.1/doc
raco setup: --- updating info-domain tables ---
raco setup: --- pre-installing collections ---
raco setup: --- installing foreign libraries ---
raco setup: --- installing shared files ---
raco setup: --- compiling collections ---
raco setup: deleting /Users/bkc39/Documents/cs/racket/mechanics/private/kernel/compiled/express_rkt.dep
raco setup: deleting /Users/bkc39/Documents/cs/racket/mechanics/private/kernel/compiled/express_rkt.zo
raco setup: deleting /Users/bkc39/Documents/cs/racket/mechanics/private/kernel/compiled/generics_rkt.dep
raco setup: deleting /Users/bkc39/Documents/cs/racket/mechanics/private/kernel/compiled/generics_rkt.zo
raco setup: deleting /Users/bkc39/Documents/cs/racket/mechanics/private/kernel/compiled/types_rkt.dep
raco setup: deleting /Users/bkc39/Documents/cs/racket/mechanics/private/kernel/compiled/types_rkt.zo
raco setup: --- parallel build using 4 jobs ---
raco setup: 3 making: <pkgs>/mechanics
raco setup: 3 making: <pkgs>/mechanics/coverage
raco setup: 3 making: <pkgs>/mechanics/coverage/assets
raco setup: 3 making: <pkgs>/mechanics/coverage/private
raco setup: 3 making: <pkgs>/mechanics/coverage/private/kernel
raco setup: 3 making: <pkgs>/mechanics/coverage/private/numerics
raco setup: 3 making: <pkgs>/mechanics/coverage/private/numerics/functions
raco setup: 3 making: <pkgs>/mechanics/coverage/private/numerics/integer
raco setup: 3 making: <pkgs>/mechanics/coverage/scribblings
raco setup: 3 making: <pkgs>/mechanics/coverage/scribblings/numerics
raco setup: 3 making: <pkgs>/mechanics/coverage/scribblings/numerics/functions
raco setup: 3 making: <pkgs>/mechanics/coverage/scribblings/numerics/integer
raco setup: 3 making: <pkgs>/mechanics/private
raco setup: 3 making: <pkgs>/mechanics/private/display
raco setup: 3 making: <pkgs>/mechanics/private/kernel
raco setup: 3 making: <pkgs>/mechanics/private/numerics
raco setup: 3 making: <pkgs>/mechanics/private/numerics/functions
raco setup: 3 making: <pkgs>/mechanics/private/numerics/integer
raco setup: 3 making: <pkgs>/mechanics/scribblings
raco setup: --- creating launchers ---
raco setup: --- installing man pages ---
raco setup: --- building documentation ---
raco setup: 3 skipping: <pkgs>/custom-load/custom-load.scrbl
raco setup: 2 skipping: <pkgs>/cover/cover/scribblings/cover.scrbl
raco setup: 3 running: <pkgs>/mechanics/scribblings/mechanics.scrbl
raco setup: rendering: <pkgs>/mechanics/scribblings/mechanics.scrbl
raco setup: --- installing collections ---
raco setup: --- post-installing collections --- Seems to build fine for me.. |
Finally! looks like this is up to date. If this is good to you let'd do it to it. |
|
||
(rename-out | ||
[Rf Carlson-elliptic₁] | ||
[Rf Carlson-elliptic-1] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make all the ascii versions be fn_N
?
Mostly, I want to be consistent. But also I think underscores are better than hyphens or nothing at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean? The scmutils
versions all use fnN
with no underscore in bessel
and fn-N
in elliptic
. I only have it this way for consistency.
k that is all. Consistent ascii names and a plea for |
Ok. Is this what you meant by consistent names? For the |
No, this isn't really what I meant with the names. I think we should give one ascii equivalent for names like (Now there's multiple names for each.) |
Like it says, we change the manually defined aliases to use
rename-out
. Looks ready to merge. I just haven't tested if the contracts also inherit when you dorename-out
. Conditional on that being true, this is good to go.