-
Notifications
You must be signed in to change notification settings - Fork 14
Should we include commented-out libcore in avr-rust? #54
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
Comments
My version is here: https://github.com/gergoerdi/rust-avr-libcore-mini I'm happy to move it wherever. It is based on
|
The big trick to me is that we need the full libcore to build the compiler for the host but when targeting AVR we need the minimized libcore for now. Commenting out wouldn't be sufficient for that, unless we actually had two directories, at which point the merge conflicts would go to zero but the updating process would get much harder ;-) Perhaps Beyond that, I'd be happy to see it present here. |
As a rough scope:
This includes changes like -#[derive(Copy, Clone, Eq, PartialEq, Ord, PartialOrd, Debug, Hash)]
+#[derive(Copy, Clone, Eq, PartialEq, Ord, PartialOrd)] Which I'm sure was annoying to do and will be annoying to bracket in |
I feel like most of the |
In the meantime, couldn't we reduce the diff considerably by keeping |
I've got great news! I've just pushed a new version of
|
The remaining changes compare to
|
|
More details on the magnitude of the difference from upstream
|
I was wondering what your thoughts were @shepmaster and @gergoerdi on pushing one of the minified versions of
libcore
you both have so that it is a part of this repo?There isn't much point in maintaining separate local
libcore
libraries.One concern is that it may mean that we get more merge conflicts. We would probably have to comment out parts of libcore in this repository anyway for stuff like float/libcore support.
The text was updated successfully, but these errors were encountered: