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
I was playing around with the prototype compiler on godbolt and ran into a frustrating problem. When I'm programming (particularly when experimenting admittedly) if I type in there is an exceedingly high chance I'm about to follow it up with t and type int. This is particularly true at the start of the declaration of a function parameter. Practically the consequence of this was that the key sequence I used to type the in keyword was almost always i+n+t+backspace which was quite annoying. I wonder if this might similarly affect tools which try to be helpful by autocompleting things for you.
Ultimately I suspect this is one of those "just deal with it situation" where over time I will retrain my fingers to not follow up in with t but if there were any good alternate contenders this might be a tie-breaker consideration.
My first thought for an alternative was input. I don't know if that would have the same issue but intuitively I think not. However input and inout are probably too similar.
The text was updated successfully, but these errors were encountered:
I was playing around with the prototype compiler on godbolt and ran into a frustrating problem. When I'm programming (particularly when experimenting admittedly) if I type
in
there is an exceedingly high chance I'm about to follow it up witht
and typeint
. This is particularly true at the start of the declaration of a function parameter. Practically the consequence of this was that the key sequence I used to type thein
keyword was almost always i+n+t+backspace which was quite annoying. I wonder if this might similarly affect tools which try to be helpful by autocompleting things for you.Ultimately I suspect this is one of those "just deal with it situation" where over time I will retrain my fingers to not follow up
in
witht
but if there were any good alternate contenders this might be a tie-breaker consideration.My first thought for an alternative was
input
. I don't know if that would have the same issue but intuitively I think not. However input and inout are probably too similar.The text was updated successfully, but these errors were encountered: