-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
std::abi #856
std::abi #856
Conversation
Just a question: Is this PR targeting the current fe implementation? I thought you would work on the std for fe-v2 after testing implementation. |
this is some non-committal sketch code, ultimately Im targeting v2. is the v2 branch stable enough to work on? |
I don't know how stable it should be for you to start working on it. At least the new parser will work. For semantics, I wouldn't add projection stuff, so basically, it's the same except for trait solving, type inference, and pointer types. As I said, some std implementations are necessary to implement v2, like encode/decode stuff. So, It'd be better for me if you start targeting v2 implementation. But it's up to you. |
c1284ea
to
2a77608
Compare
@@ -297,3 +297,48 @@ pub struct RawCallBuffer { | |||
return self.buf.writer() | |||
} | |||
} | |||
|
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.
delete this
What was wrong?
How was it fixed?
To-Do
OPTIONAL: Update Spec if applicable
Add entry to the release notes (may forgo for trivial changes)
Clean up commit history