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.

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

toLeopard: Review uses of "any"-shape inputs for string operations #152

Open
towerofnix opened this issue Jul 2, 2024 · 0 comments
Open
Labels
compatibility Mismatch or currently unsupported language behavior fmt: Leopard Pertains to Leopard format (JavaScript)

Comments

@towerofnix
Copy link
Member

There are various places where we use InputShape.Any (or inputToJS without any desired traits, after #150) for inputs that would ostensibly take or expect strings. Sometimes this might be alright - but shouldn't these all be string inputs? Wouldn't some of them error if a number-like literal gets converted to a JS number primitive? Demands investigation.

@towerofnix towerofnix added compatibility Mismatch or currently unsupported language behavior fmt: Leopard Pertains to Leopard format (JavaScript) labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility Mismatch or currently unsupported language behavior fmt: Leopard Pertains to Leopard format (JavaScript)
Projects
None yet
Development

No branches or pull requests

1 participant