Skip to content
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

refactor CCIO #261

Closed
3 tasks done
c-cube opened this issue May 31, 2019 · 2 comments
Closed
3 tasks done

refactor CCIO #261

c-cube opened this issue May 31, 2019 · 2 comments
Assignees
Milestone

Comments

@c-cube
Copy link
Owner

c-cube commented May 31, 2019

@c-cube c-cube added this to the 3.0 milestone May 31, 2019
@c-cube c-cube self-assigned this May 31, 2019
@Drup
Copy link
Collaborator

Drup commented May 31, 2019

  • Make code that triggers use-after-free harder to write than correct code

@c-cube
Copy link
Owner Author

c-cube commented May 31, 2019

Maybe the gen/seq operators need to be in an Unsafe module with docs (and attribute-backed messages?) explaining the lifetime situation. Toplevel operators would provide list/fold/iter stuff.

c-cube added a commit that referenced this issue Nov 12, 2019
deprecate the previous versions
see #261
@c-cube c-cube closed this as completed Dec 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants