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

Address inlinability/rewrite rules better #63

Open
treeowl opened this issue Dec 1, 2022 · 0 comments
Open

Address inlinability/rewrite rules better #63

treeowl opened this issue Dec 1, 2022 · 0 comments

Comments

@treeowl
Copy link
Collaborator

treeowl commented Dec 1, 2022

Notably, the m >>= f unfolding looks something like fromViewT <a loop breaker>. That means that if m is itself fromViewT whatsit, we won't be able to rewrite toViewT (fromViewT whatsit) to whatsit. That seems sad.

I haven't been able to figure out a way to turn lift m >>= lift . f to lift (m >>= f). Is there some way we can arrange things so that falls out?

Is there something we can do about it? Also: it seems kind of random what's INLINE and what's INLINABLE. Let's figure out what it should be and why and write notes.

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

No branches or pull requests

1 participant