Skip to content

Replace TypeSignature::String with TypeSignature::Coercible #14759

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
jayzhan211 opened this issue Feb 19, 2025 · 1 comment · Fixed by #14917
Closed

Replace TypeSignature::String with TypeSignature::Coercible #14759

jayzhan211 opened this issue Feb 19, 2025 · 1 comment · Fixed by #14917
Assignees
Labels
enhancement New feature or request

Comments

@jayzhan211
Copy link
Contributor

jayzhan211 commented Feb 19, 2025

Is your feature request related to a problem or challenge?

After #14440, we can use Coercible signature for existing String

                    TypeSignature::Coercible(vec![
                        Coercion::new_exact(TypeSignatureClass::Native(logical_string())),
                    ]),

Describe the solution you'd like

No response

And deprecate TypeSignature::String

Describe alternatives you've considered

No response

Additional context

#14440
#13301

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants