But does it scale?
-
-
-
Hmm... there will be probably some contention for those `true` and `false` boolean values if they are accessed from multiple threads. Should the method return `Task<bool>` instead?


- Još 2 druga odgovora
Novi razgovor -
-
-
Nice! But you missed the unit tests
-
And there is a typo...
Kraj razgovora
Novi razgovor -
-
-
No try-catch in there just to be sure.
-
try { ... } catch { /* wait and retry */ Thread.Sleep(100); return value.IsTrue(); }
Kraj razgovora
Novi razgovor -
-
-
Oddly, I have just had to do something like this... except it checks whether a value is null. The reason is, CLR seems to think a null variable (as seen in the debugger as null) is not null in an if statement. So I created a property which tracks null through a bool. :(
-
Interesting. Can you post or send me the complete example?
Kraj razgovora
Novi razgovor -
-
-
Uh... I'm trying to wrap my head around this... if (!true && !false) return true


- Još 3 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
