Skip to content

Resolve the static region during typechecking, not in the parser #2256

Closed
@catamorphism

Description

@catamorphism
Contributor

As per a FIXME in the parser (region_from_name): "To be consistent with our type resolution, the static region should probably be resolved during type checking, not in the parser."

Activity

catamorphism

catamorphism commented on Aug 23, 2012

@catamorphism
ContributorAuthor

This appears to be no longer an issue, since the FIXME has gone away.

added a commit that references this issue on Jun 30, 2023

Auto merge of rust-lang#10909 - Alexendoo:useless-for-in-vec, r=llogiq

e2c655b
added a commit that references this issue on Feb 25, 2025

Merge pull request rust-lang#2256 from torfsen/fix-examples-for-night…

342ced9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

A-frontendArea: Compiler frontend (errors, parsing and HIR)A-type-systemArea: Type systemC-cleanupCategory: PRs that clean code up or issues documenting cleanup.

Type

No type

Projects

No projects

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @nikomatsakis@catamorphism

      Issue actions

        Resolve the static region during typechecking, not in the parser · Issue #2256 · rust-lang/rust