Prelude functions should be conventionally "data first" #80

New Issue

scott · 2025-07-06T06:04:34Z

scott commented

2025-07-06 06:04:34 +00:00

I need to have a convention; it might as well be "data first," even though we don't have currying.

So at (xs, idx), contains? (xs, val), slice (xs, idx), etc.

I need to have a convention; it might as well be "data first," even though we don't have currying. So `at (xs, idx)`, `contains? (xs, val)`, `slice (xs, idx)`, etc.

scott added the

feature

design

labels 2025-07-06 06:04:34 +00:00

scott added this to the Core: CC2 milestone 2025-07-06 06:04:38 +00:00

scott commented

2025-07-06 20:59:27 +00:00

Done, as of a few commits ago.

The exception to this are the three (well, four) functional iteration functions, fold, foldr, map, and filter, which are function-first. Which makes a certain amount of sense. Not going to change them now.

Done, as of a few commits ago. The exception to this are the three (well, four) functional iteration functions, `fold`, `foldr`, `map`, and `filter`, which are function-first. Which makes a certain amount of sense. Not going to change them now.

scott closed this issue

2025-07-06 20:59:27 +00:00

Sign in to join this conversation.