Skip to content

Fix CharInClass reference in regex emitter - #61559

Merged
stephentoub merged 1 commit into
dotnet:mainfrom
stephentoub:fixglobal
Nov 15, 2021
Merged

Fix CharInClass reference in regex emitter#61559
stephentoub merged 1 commit into
dotnet:mainfrom
stephentoub:fixglobal

Conversation

@stephentoub

Copy link
Copy Markdown
Member

We've tried to consistently use global:: whenever referring to core library types in the regex generator emitted code. I'd missed these two.

(That said, these make the code a lot harder to read, especially in places where we're unable to use extension methods as extensions, so we'll want to revisit this policy.)

cc: @joperezr

We've tried to consistently use global:: whenever referring to core library types in the regex generator emitted code. I'd missed these two.
(That said, these make the code a lot harder to read, especially in places where we're unable to use extension methods as extensions, so we'll want to revisit this policy.)
@ghost

Copy link
Copy Markdown

Tagging subscribers to this area: @eerhardt, @dotnet/area-system-text-regularexpressions
See info in area-owners.md if you want to be subscribed.

Issue Details

We've tried to consistently use global:: whenever referring to core library types in the regex generator emitted code. I'd missed these two.

(That said, these make the code a lot harder to read, especially in places where we're unable to use extension methods as extensions, so we'll want to revisit this policy.)

cc: @joperezr

Author:stephentoub
Assignees:-
Labels:

area-System.Text.RegularExpressions

Milestone:-

Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@stephentoub@joperezr