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.

Sign up for GitHub

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

Jump to bottom

Making "tailcall" part of the function signature #113

Closed
jfbastien opened this issue Nov 3, 2017 · 2 comments
Closed

Making "tailcall" part of the function signature #113

jfbastien opened this issue Nov 3, 2017 · 2 comments
Assignees
@rossberg

Comments

@jfbastien
Copy link
Member

Action item: Andreas to explore making “tailcall” part of function signatures, and document why he thinks this has bad implications. Michael / Luke to synchronize on why it would be useful to them.
@jfbastien
Copy link
Member Author

jfbastien commented Apr 23, 2018 •
edited
Loading

At the Fastly in-person meeting we took the following poll:

POLL: We want to consider proceeding in a different direction than what Andreas has proposed, based on data that Michael will collect.

SF | F | N | A | SA
6 | 4 | 12 | 3 | 0

@fgmccabe
Copy link
Collaborator

Closing this, we have settled on not having special signatures for tail call functions.

fitzgen pushed a commit to fitzgen/meetings that referenced this issue Sep 14, 2023
@esoterra
Merge pull request WebAssembly#113 from bytecodealliance/Kylebrown9-p…
f5eaaae 
…atch-1

Submit SIG-Guest-Languages Notes for July 11th, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rossberg rossberg

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jfbastien @fgmccabe @rossberg