Skip to content
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

Jump to bottom

[BUG] NoCheck<string | null> or NoCheck<string | undefined> fails with "Maximum call stack exceeded" #29

Closed
FredTreg opened this issue Jul 30, 2023 · 0 comments
Closed

[BUG] NoCheck<string | null> or NoCheck<string | undefined> fails with "Maximum call stack exceeded" #29

FredTreg opened this issue Jul 30, 2023 · 0 comments

Comments

@FredTreg
Copy link
Contributor

FredTreg commented Jul 30, 2023 •
edited
Loading

Describe the bug
When using an Assert<> on a type with a NoCheck<sometype | null> field, the compiler fails with RangeError: Maximum call stack size exceeded.

The same happens with undefined.

Playground link
playground

Expected behavior
Compiler does not fail

Additional context
0.3.2
@FredTreg FredTreg changed the title [BUG] NoCheck<string | null> or Nocheck<string | undefined> fails with "Maximum call stack exceeded" [BUG] NoCheck<string | null> or NoCheck<string | undefined> fails with "Maximum call stack exceeded" Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FredTreg