5 ms·

I anticipated my own falsity. I'm aware and at home with it

• eru 6y ago
  Huh? Why do you say something that you anticipate to be false?
  • tsegratis 6y ago
    Simply bervity I anticipated I could well be wrong. I ALSO anticipated it would be a hard statement for people to take I think it was a reasonable statement -- I can't research everything I say, and I had read re2 and regexes in rust to be the same Interesting to read about redgrep and derivatives approach. Currently I'm programming a language that adds turing completeness to PEG expressions -- as in functions, but extended so the lhs is like a PEG -- just as function body can call sub functions, so too can the lhs I'm hoping this will give a simple unified language -- Philosophically: We make mistakes. If we can't handle that, then either we don't speak or program; or we deny it, program in c, then have flamewars and real wars Or thirdly, we accept it, program in rust, and let others correct us We can say you are my rustc compiler. So in effect I used a rust philosophy..... While programming in c
    • tsegratis 6y ago
      In one word: Jesus
    • mplanchard 6y ago
      I guess the thing is that if we’re not sure whether or not what we’re saying is true, it can be considerate to phrase it that way, e.g. “I think ripgrep’s regex library is written in C” rather than stating it as a fact. While it is particularly likely that folks on this website will correct mistaken statements, stating them as fact seems more likely to potentially spread misinformation. But anyways, cheers and good luck with your programming language!