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

add ring cut notion to padring #71

Merged
merged 1 commit into from
Aug 27, 2024
Merged

add ring cut notion to padring #71

merged 1 commit into from
Aug 27, 2024

Conversation

gadfort
Copy link
Contributor

@gadfort gadfort commented Aug 15, 2024

Closes #64

@gadfort gadfort force-pushed the iocut branch 2 times, most recently from d18cda3 to 86c57ed Compare August 15, 2024 20:54
Copy link
Member

@aolofsson aolofsson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Possibly just a documentation question, but we should have a clear definition of before and next. Lambdalib is genereric so we don't want to be prescriptive about ordering and methodology. As long as the definition is written down and consistent (in multiple places).

I think your definition "before and next" makes sense in the context of ioside and the 0/1 index is probably better than my left/rightedness (too prescriptive).

Can you add a few sentences in the README that explains the restrictoins/guidelines for usign la_iocut.

Base automatically changed from padring-lib to main August 16, 2024 12:21
@gadfort gadfort linked an issue Aug 16, 2024 that may be closed by this pull request
@aolofsson aolofsson merged commit 47854f0 into main Aug 27, 2024
3 checks passed
@aolofsson aolofsson deleted the iocut branch August 27, 2024 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement support for la_iocut
2 participants