Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Gavin91001yBEST WAY TO FIND AND RECOVER YOUR STOLEN BITCOIN?_RED CYBER HACKER..
I’m writing to the public to provide knowledge about RED CYBER HACKER. Look no further if you ever demand hacking services, When I lost more than $150,000 USD in bitcoin, individually I found myself in a challenging situation, I was inconsolable and believed I had reached my lowest point, I had no hope of getting my invested money back. All that changed when I discovered RED CYBER HACKER and everything was transformed. The company intervened and helped me get all my money back within a short period of time. Their services are well recommended and they ensure maximum satisfaction to their clients. You can contact them via
Email: redcyberhacker 153 @ gmail com
WhatsApp: +1..9..4..5..2..0..6..0..7..1..1
Telegram: +1..9..4..5..2..0..6..0..7..1..1 -
@retoor C# has built-in support for source generators (used for xaml and protobuf among others), but to do this correctly you probably need to import the lexer from Roslyn to make sure that you only apply the transform where it's actually needed.
-
I'd say 2 days because anything that works with source code has to be tested to hell and I don't yet know whether I can run just the lexer or if I have to add a patched version of Roslyn into the repo to access a private API.
-
@retoor Parsing and then serializing is the correct way to transform structured data like source code. You can get away with less if you can confidently say that you won't need any more features, but I spent my last half a year adding features to programs that were developed with that assumption in 2008 and have been continuously receiving new feature requests since then.
-
@retoor I mean, to properly check whether you're in a string you already need a decent sized parser because C# has like 4 different kinds of strings and one of them (interpolated $-strings) is a recursive grammar. And once you have that, you're assuming that new string types aren't going to be added to the language.
besides, where did this requirement come from? Do we know that similar but separate features won't be coming soon? We probably don't.
1/2 -
2/2
I wanted to write a script to autogenerate fixtures for a new type of gizmo the company may sell, but I got shot down because we only need to do that like once every few years. Since then, every month we added a new type of gizmo, 4 in total. And if I had written that script in like a week, we could've also written a test suite for the gizmo type definition system.
Doing things properly has hidden savings, probably way more of them than you realize. The only reason I'd do a shitty string replacer is for market research if we're not actually sure we need this, but even then I'd have to trust my managers to let me write it properly once the value has been asserted.

Hair... Hehe
joke/meme