-
Notifications
You must be signed in to change notification settings - Fork 46
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
Suggestion: Optional arity for exports #63
Comments
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Dec 30, 2016
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Dec 30, 2016
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 2, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 2, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 2, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 2, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 3, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 3, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 3, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 3, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 3, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
make_modules/1 takes a list of source code strings to parse and rewrite as proper modules with imports and exports expanded. Expanded exports now work so we can do things like `export foo` instead of `export foo/1, foo/2`. Rewriting functions not defined in the module to inter-module calls using imports is not yet done but I think because of the increasing amount of changes it's worth integrating now, if only to get the export changes in. Fixes alpaca-lang#63
j14159
added a commit
to j14159/alpaca
that referenced
this issue
Jan 7, 2017
This was suggested in alpaca-lang#63. It's not actually part of the AST generation phase yet but it made sense to handle this at the same time as function imports for alpaca-lang#62. I'm going to decouple the basic parsing pass from the renaming and rewriting pass of the parser since rewriting the names of imported functions to inter-module calls will require the other modules to already be parsed and accessible.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It often is frustrating to update arity for changed functions' signatures. While there are definitely cases when one would keep some functions out from being exported, often times the need to maintain arity in
export
becomes a nuisance.My proposal is to make arity specification in
export
optional, and if it isn't specified, export all functions with a given name, regardless of arity.The text was updated successfully, but these errors were encountered: