Permalink
10000
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 17 commits
- 0 files changed
- 1 contributor
Commits on May 10, 2021
-
Create compile-time values for base ftypes.
Converted built-in foreign types to work like other ftypes using a compile-time value to specify the value of the foreign type. primdata.ss, ftype.ss
-
Commits on Sep 7, 2021
-
Revert "Create compile-time values for base ftypes."
This reverts commit 3b6d525.
-
-
Alternative fix for native ftypes.
updated ftypes to allow native ftypes to be used even if another non-ftype syntactic binding for the type exists. for instance, if a syntactic binding for integer-32 is introduced which is not bound to an ftd, using integer-32 in the context of an ftype will still work. this change also allows an ftype binding to be created for a native type by using (define-ftype <native-type> <native-type>), allowing users to create standard ftype bindings for the native-types if that is preferred. s/ftype.ss
Commits on Sep 13, 2021
-
Adding some tests for ftype changes.
Added a couple of tests for the ftype change to avoid having syntactic bindings overlap the native ftype names without interfering with the operation of ftype definitions. This also includes a fix to the CSUG ftype section, thanks to Oscar Waddell for the change.
-
Commits on May 8, 2022
Commits on May 9, 2022
-
Fix the
char-function to return negative integers.fixed a bug in `char-` that lead to returning a large positive integer result when the second argument had a value greater than the first. It now returns a negative number in this situation. cpnanopass.ss 5_4.ms root-experr-* patch-*
-
Commits on Aug 13, 2023
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...main