You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry, made a mistake in the title--this is for function arguments, although it might also apply (to a slightly lesser extent) to fields in a struct.
The reason I'd like a blue squiggly is because new users often make the mistake of overtyping their functions. It's very rare that you actually need a function to only allow Float64s.
I strongly disagree with this suggestion. I write lots of high-performance code (e.g., MultiFloats.jl) that depends on exact bitwise representation, so my functions are correctly and appropriately specialized to concrete types.
Maybe you don't write code like that, and that's fine, but I think this is way too opinionated to turn on in the linter by default.
e.g. Float64 here:
![image](https://private-user-images.githubusercontent.com/71727937/239363043-c5322d87-e4ba-4d2e-849b-bfcb336a2479.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0MDIxMzEsIm5iZiI6MTczOTQwMTgzMSwicGF0aCI6Ii83MTcyNzkzNy8yMzkzNjMwNDMtYzUzMjJkODctZTRiYS00ZDJlLTg0OWItYmZjYjMzNmEyNDc5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDIzMTAzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQwZTVkZTVhYTc1NTljZWI4MTdjOWFjYThlZGM0YzJiY2Y5N2NkNDc0ODBjYjVlZjIwNTQ3Yzk2ZDNjMmJlMmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.vsn8pqLIp_LMF0JZZeFN7mPUfFQTQYV6FWJWZ29_Jtw)
The text was updated successfully, but these errors were encountered: