-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Use a gensym to store doc metadata #12062
Conversation
Could you use |
Possibly, but this is very much an implementation detail that people in general aren't going to look at. The actual meta dict in your module is going to be called something like |
(In fact, we sort of are optimising for user surprise here – it's as surprising as is reasonably possible exactly so that people don't come across it by accident). |
(Whoops, totally forgot to go and implement this after opening #11974... sorry about that.) Re: using a |
Well, I saw it, and scratched my head! Is the META' name not saved anywhere then? |
Use a gensym to store doc metadata
How about we just call the constant in every module |
Sure, I'm completely OK with that too. |
I hope you do keep the meta function, that is precisely what's being talked about elsewhere, as being more Julian than accessing a field. |
Done in 4fc9bb6 |
What should the official interface for getting at the metadata be then? |
Proposed fix for #11974. Would a constant symbol like
__META__
buy us anything over this approach?