-
Notifications
You must be signed in to change notification settings - Fork 74
rust: add libcore to certification doc #2249
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
base: main
Are you sure you want to change the base?
Conversation
|
|
9530c28 to
42e6cd2
Compare
|
The created documentation from the pull request is available at: docu-html |
42e6cd2 to
ad9c087
Compare
|
before this goes out of draft, I will try to use feroceen compiler to recheck if there are more gaps hidden inside libcore specific modules. Currently our codebase support cargo, so it may be that I will use cargo for that. |
ad9c087 to
3f41012
Compare
| Certified libcore | ||
| ################# | ||
|
|
||
| .. tool_req:: Rust libcore |
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.
Thanks for starting here. Can you add also something here, https://eclipse-score.github.io/score/main/score_tools/index.html, which is more or less the evaluation result to motivate, that we need the qualification here for the different elements
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.
I would do it in seperate PR once I obtain more info from Feroceen about the compiler itself. The libcore is just the library part. I will also propose to tak eover Feroceen aproach for TCL and all tooling assesment for other tools we need in rust scope
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.
Fine for me, thank you
|
This PR is stale because it has been open for 30 days with no activity. It will be closed in 10 days if no further activity occurs. #magic___^_^___line |
Fulfills: #2020
WIP: Still looking into empty internal modules at the certification part.