-
Notifications
You must be signed in to change notification settings - Fork 126
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
Naming conventions and strategies throughout OSCAR #1714
Comments
I don't think the soon to be introduced |
On Fri, Nov 11, 2022 at 08:02:24AM -0800, Tommy Hofmann wrote:
I don't think the soon to be introduced `quotient_ring` has any relation to `quo`.
I think it has - and there are already various quotient_rings that
sneaked in...
… --
Reply to this email directly or view it on GitHub:
#1714 (comment)
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
I think that we should have this discussion in person -- not with erveryone typing in a github issue (and maybe only sum up the results here afterwards for later reference). To your examples above just one remark: |
Another one: |
Some first steps have been taken in #1738 . |
For consistency and user friendliness across the many different areas of
OSCAR
, it might be good to discuss and ideally agree on the following.Naming conventions:
quotient_ring
vs.quo
,residue_ring
vs.quo
,subscheme
vs.sub
orclosed_sub
,hypersurface_complement
vs.open_sub
,ambient_affine_space
vs.ambient_space
(isaffine
not implicitly clear?)Strategies:
The text was updated successfully, but these errors were encountered: