Add explicit tests for unconstrained type param not being assignable to {}
and Record<string, any>
#48421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #48366 .
The PR only mentions adjusted assignability rules for
{}
and I was wondering if this has affectedRecord<string, any>
as well. So I've tried it out locally and it turns out that yeah - it did. Those types might be very similar for the compiler so maybe that's a "given" but for a layman like me - this wasn't that obvious.cc @weswigham