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

Inline vs. Inlinable? #60

Open
isturdy opened this issue May 31, 2013 · 0 comments
Open

Inline vs. Inlinable? #60

isturdy opened this issue May 31, 2013 · 0 comments

Comments

@isturdy
Copy link
Contributor

isturdy commented May 31, 2013

member is marked INLINABLE while notMember is marked INLINE, despite both habing essentially identical structure. Other things that are INLINE while similar functions are INLINABLE: foldlWithKeyWith, foldrWithKeyWith (in these cases I would expect the API wrapper functions to be INLINE and the longer core function INLINABLE, if anything), updateExtremity.

Functions missing any such pragma that I think may want one: null, empty, elems, assocs, keys, unionWith, unionWithKey, unions, unionsWith, intersectionWithKey, map, mapKeys, toAscList, toDescList, filter.

Is there some reason to these decisions that I have overlooked?

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