https://github.com/pauleveritt/andrey_abstract

Research with @vlasovskikh ideas about registries and abstract classes.
https://github.com/pauleveritt/andrey_abstract

Last synced: about 4 hours ago
JSON representation

Research with @vlasovskikh ideas about registries and abstract classes.

• Host: GitHub
• URL: https://github.com/pauleveritt/andrey_abstract
• Owner: pauleveritt
• Created: 2021-01-27T18:49:24.000Z (almost 4 years ago)
• Default Branch: master
• Last Pushed: 2021-02-08T18:20:17.000Z (over 3 years ago)
• Last Synced: 2024-10-10T19:22:13.574Z (26 days ago)
• Language: Python
• Size: 17.6 KB
• Stars: 0
• Watchers: 4
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Interface Registry Experiment

Working with @vlasovskikh on a `wired`-style registry alternative using abstract class/method/member ideas instead of

protocols.

## Questions

0. Look at mypy warning.s

   

1. Is it wrong to use (abstract) classes as keys?

2. Let's add an example of "protecting" attributes.

3. Could we move the global registry to a class variable on each "directive" and use `__init_subclass__` to register?

4. Could you have "directives" that didn't subclass, but were just explicitly registered? Meaning, 

   `registry.register_class(View, CustomerView)` would work even if `CustomerView` didn't subclass.

   (This would be more of a protocol-ish, structural approach.)  

   

5. Is Java `interface` *really* part of nominal typing?