QPQ-AG/sophia
10
0
Fork 0
Code Issues 41 Pull Requests 5 Actions Packages Projects Releases 16 Wiki Activity

Introduce pipe operator |> #862

Merged
ghallak merged 3 commits from ghallak/230 into master 2022-04-12 18:40:32 +09:00
Conversation 7 Commits 3 Files Changed 7 +41 -6
ghallak commented 2022-02-28 19:41:22 +09:00 (Migrated from gitlab.com)
Copy Link

Fixes: #230

Fixes: #230
ghallak commented 2022-02-28 20:17:08 +09:00 (Migrated from gitlab.com)
Copy Link

Runtime tests: 3054792ba6/test/contracts/pipe_operator.aes

Runtime tests: https://github.com/ghallak/aeternity/blob/3054792ba66e4086075af9713b064c8eb8d673f9/test/contracts/pipe_operator.aes
ghallak commented 2022-02-28 20:23:25 +09:00 (Migrated from gitlab.com)
Copy Link

For consistency, should this be called pipe operator or reverse application operator? 🤔

For consistency, should this be called pipe operator or reverse application operator? :thinking:
zxq9 commented 2022-04-11 18:56:24 +09:00 (Migrated from gitlab.com)
Copy Link

Created by: radrow

Review: Dismissed

I think it would be nicer to make it behave just like in Elixir, so you could do

[1,2,3,4] |> List.flat_map(x => [x, -x])

Note the "partial" application of flatmap. Specifically, to let autocurry functions if needed (and fully applied). @ghallak @hanssv what do you think?

This could be a scope of another PR though

*Created by: radrow* **Review:** Dismissed I think it would be nicer to make it behave just like in Elixir, so you could do ``` [1,2,3,4] |> List.flat_map(x => [x, -x]) ``` Note the "partial" application of flatmap. Specifically, to let autocurry functions if needed (and fully applied). @ghallak @hanssv what do you think? This could be a scope of another PR though
ghallak commented 2022-04-11 19:10:50 +09:00 (Migrated from gitlab.com)
Copy Link

@radrow You suggestion seems good, but since we don't have partial application currently, this might be done in another PR.

@radrow You suggestion seems good, but since we don't have partial application currently, this might be done in another PR.
zxq9 commented 2022-04-12 01:09:30 +09:00 (Migrated from gitlab.com)
Copy Link

Created by: radrow

Review: Approved

*Created by: radrow* **Review:** Approved
zxq9 commented 2022-04-12 18:31:54 +09:00 (Migrated from gitlab.com)
Copy Link

Created by: hanssv

Review: Approved

*Created by: hanssv* **Review:** Approved
zxq9 commented 2022-04-12 18:40:32 +09:00 (Migrated from gitlab.com)
Copy Link

Merged by: ghallak at 2022-04-12 09:40:32 UTC

*Merged by: ghallak at 2022-04-12 09:40:32 UTC*
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
WIP
bug
consensus-breaking
dependencies
documentation
duplicate
effort: high
effort: low
effort: medium
effort: trivial
enhancement
good first issue
help wanted
invalid
maintenance
question
task/feature
todo-in-rewrite
wontfix
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
pig lipstick
Muggle-facing enhancements
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QPQ-AG/sophia#862
No description provided.
Delete Branch "ghallak/230"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?