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

Move ClassRegistry and ModuleRegistry trait definitions to artichoke-core #666

Closed
lopopolo opened this issue May 9, 2020 · 1 comment · Fixed by #1355
Closed

Move ClassRegistry and ModuleRegistry trait definitions to artichoke-core #666

lopopolo opened this issue May 9, 2020 · 1 comment · Fixed by #1355
Labels
A-core Area: Core traits and interpreter-agnostic Ruby Core and Ruby stdlib implementations. A-vm Area: Interpreter VM implementations.

Comments

@lopopolo
Copy link
Member

lopopolo commented May 9, 2020

GH-661 introduces a new ClassRegistry and ModuleRegistry trait. These traits are defined in artichoke-backend. Move them into artichoke-core.

@lopopolo lopopolo added A-core Area: Core traits and interpreter-agnostic Ruby Core and Ruby stdlib implementations. A-vm Area: Interpreter VM implementations. labels May 9, 2020
@lopopolo
Copy link
Member Author

lopopolo commented May 9, 2020

😈

@lopopolo lopopolo added the E-easy Call for participation: Experience needed to fix: Easy / not much. label May 9, 2020
@lopopolo lopopolo removed the E-easy Call for participation: Experience needed to fix: Easy / not much. label Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-core Area: Core traits and interpreter-agnostic Ruby Core and Ruby stdlib implementations. A-vm Area: Interpreter VM implementations.
Development

Successfully merging a pull request may close this issue.

1 participant