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
@RicardoLuis0 had the thought of adding a warning when it comes to converting strings into specific types, i.e. colors. As we were helping someone figure out why their code was running slowly, it became apparent that was the cause of their performance issues.
Perhaps it would be wise to add a warning to some types of conversions (or all of them if it hits the same)?
The text was updated successfully, but these errors were encountered:
That'd lead to annoying warnings when people do it intentionally in contexts where it won't cause performance issues.
More annoying warnings make real warnings end up being ignored.
it'd just be for color really, that's the one super expensive conversion, and only for implicit conversions, so with String s = ...; Color c = s; would give a warning but Color c = Color(s); wouldn't
@RicardoLuis0 had the thought of adding a warning when it comes to converting strings into specific types, i.e. colors. As we were helping someone figure out why their code was running slowly, it became apparent that was the cause of their performance issues.
Perhaps it would be wise to add a warning to some types of conversions (or all of them if it hits the same)?
The text was updated successfully, but these errors were encountered: