Skip to content

ban type parameters for macros #2976

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

Merged
merged 1 commit into from
Apr 4, 2023
Merged

ban type parameters for macros #2976

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions working/macros/feature-specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,6 @@ Authors: Jacob MacDonald, Bob Nystrom

Status: **Work In Progress**

### Changelog

- *2022/01/25:* Specify that identifiers in strings can only refer to local
declarations.

## Introduction

The [motivation][] document explains why we are working on static
Expand Down Expand Up @@ -416,6 +411,11 @@ constructors are invoked, and their limitations.
- All macros must implement at least one of the `Macro` interfaces.
- Macros cannot be abstract.
- Macro classes cannot be generated by other macros.
- Macro classes cannot contain generic type parameters.
- It is possible that in the future we could allow some restricted form of
generic type parameters for macro classes, but it gets tricky because the
types in the user code instantiating the macro are not necessarily present
in the macros own transitive imports.

*Note: The Macro API is still being designed, and lives [here][api].*

Expand Down