Skip to content

RFC: Support Variadic User-Defined Type Functions #117

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

TenebrisNoctua
Copy link

@cheesycod
Copy link

cheesycod commented May 5, 2025

Personally, I fully disagree with the rfc on the basis that it’ll probably lead to postponing the new type solvers release by several months if not years due to all the bugs that’ll probably arise from variadic type functions etc. and I think it’s more important to get all the bugs fixed first over adding new features (and this one, from a cursory read, feels pretty complicated implementation wise)

Other than that, I personally fully agree with the idea.

@TenebrisNoctua
Copy link
Author

Personally, I fully disagree with the rfc on the basis that it’ll probably lead to postponing the new type solvers release by several months if not years due to all the bugs that’ll probably arise from variadic type functions etc. and I think it’s more important to get all the bugs fixed first over adding new features (and this one, from a cursory read, feels pretty complicated implementation wise)

Other than that, I personally fully agree with the idea.

I understand the concern, but I believe it won't cause any important delays for the new type-solver's release.
I also don't see the potential for many bugs either, it behaves the same as normal variadic functions, except now it's in the type-runtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants