Skip to main content
10 events
when toggle format what by license comment
Apr 8 at 3:12 comment added Karl Knechtel Do you want the correction to be specific to underscores? Or should it also be able to pick up other common-sense typos (single character errors, transpositions...)? Aside from that, what about users who don't want the compiler to apply such corrections (since it denies them the opportunity to verify)?
Apr 5 at 23:05 comment added Barmar Do you really need to do this in the language? This is something that should be in the editor, not the language.
Apr 5 at 15:49 comment added Bergi Please remove all those horizontal lines, they make the question really hard to read.
Apr 5 at 9:16 history became hot network question
Apr 5 at 5:00 history edited Michael Homer CC BY-SA 4.0
edited tags
Apr 5 at 2:07 answer added Michael Homer timeline score: 3
Apr 5 at 1:43 comment added kaya3 The only sane reason to check for this is to give suggested completions which are robust to misspellings (e.g. if the user writes foo.ascii_ then .asciiletters is still offered as a suggestion), or suggested fixes in error messages (e.g. if the user writes foo.ascii_letters, the error message says "no attribute named ascii_letters, did you mean asciiletters?"). Actually compiling a misspelled attribute as if it had been spelled correctly is dangerous; it creates a hazard in case a new attribute is added later with the other name. Fixing typos is easy; fixing bugs like that is hard.
Apr 5 at 1:24 comment added Michael Homer When you say "misspelled" class attributes in the title, are you referring specifically to these surplus/omitted underscores in their names only, or to misspellings more broadly?
S Apr 5 at 1:14 review First questions
Apr 5 at 5:01
S Apr 5 at 1:14 history asked Samuel Muldoon CC BY-SA 4.0