@TracketPacer replied to a tweet by @TracketPacer:
DoS link https://www.tiktok.com/t/ZTRW3DJhd/
@TracketPacer replied to a tweet by @TracketPacer:
DoS link https://www.tiktok.com/t/ZTRW3DJhd/
[erica from stranger things voice] JUST the FACTS
@LolOverruled ("Lolo") retweeted:
@kandistmallett ("Kandist") replied to a tweet by @kandistmallett:
Cop City is a testament to the battles that will need to be forged. Solidifying what many of us in the struggle have long known to be true: that our movements are not isolated, that oppressors overlap, and that the climate crisis and the need to abolish the police are interwoven.
@LolOverruled ("Lolo") wrote:
Imagine if everyone who went on Freedom Rides was arrested for Domestic Terrorism. Complete and utter bullshit. Stop Cop City! Support @defendATLforest
with quote tweet:
@theintercept ("The Intercept") wrote:
“It’s collective punishment. The police are trying to establish a de-facto norm that anyone who associates with a political movement will be attacked and charged for the actions of any other supporter of that movement.” https://interc.pt/3ZFVZn1
@RachelAppel ("Rachel Appel") retweeted:
@cwoodruff ("Chris Woodruff "Woody"") wrote:
Very cool about the new MAUI Layout Inspector in @JetBrainsRider
@RachelAppel ("Rachel Appel") wrote:
American friend asks "Working on anything fun today?"
Me: "Järliche Sicherheitsunterweisung and Bildschirmarbeitsplätze"
Friend: 😶
@fakedansavage ("Dan Savage") retweeted:
@RogersParkMan ("Bill Savage") wrote:
What’s more anachronistic in this Hocus-Focus? Men wearing hats, or men reading newspapers? @NeilSteinberg
@fakedansavage ("Dan Savage") wrote:
Not the obituary I wanted to read today.
@mr_modular ("Allen Nemo") retweeted:
@benryanwriter ("Benjamin Ryan") wrote:
Gays about Chick-fil-A:
“But it’s such good chicken!”
@djco ("Dirkjan Ochtman (@djc@hachyderm.io)") wrote:
This was fun!
with quote tweet:
@jonkers_erik ("Erik Jonkers") wrote:
Delft meetup complete! Proud of a tremendous @rustembedded line-up, wrapped up with a great Q&A by @djco with @m_ou_se!
Thanks @Geoxion, Sjors (@jittercompany), @jdonszelmann and to everyone that joined and helped out.
Slides and (fingers crossed) recordings to follow.
@meakoopa ("Anthony Oliveira") retweeted:
@Williesillie2 ("Willie Muse") wrote:
I had a wedding for my cat and dog
with quote tweet:
@BBCWorld ("BBC News (World)") wrote:
Mental-health crisis from pandemic was minimal, study suggests https://bbc.in/3ZA0EHd
@meakoopa ("Anthony Oliveira") retweeted:
@eerie0013529 ("{♡〕") wrote:
babe are you ok your being weird as fuck
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
So, we'll change the spec to match the actual implementation, and we'll make sure that Kotlin 2.0 works just like Kotlin 1.0 here, modulo the type-inference in some corner cases where the current compiler produces code that crashes, but that is a story for another time. /Done
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
So, we've looked at it again based on two factors: avoid breaking existing Kotlin code, and follow the principle of least surprise -- the code should work just as you expect it to. /10
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
In Kotlin design philosophy, the right way to do things cannot require you to write more code. So we have to support the simple and short code that coerces the value in the setter. /9
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
We've decided that the first behavior that outputs 0 is the least puzzling one for a person who defined the property setter to coerce the value. I'm happy it matches the result of my twitter poll. /11
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
You can say that's the wrong way to coerce the values. That the right way is to define a custom type with all the math operations that always keep the property in range, and then define the property of that type. But that is a lot of code! /8
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
It is Ok to change the behavior in Kotlin 2.0 to match the published spec. Right? Not so fast. During the original discussion, we failed to bring to the table the case with setter that coerces the value. Turns out, there is quite a lot of such Kotlin code in the wild. /7
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
So, why this would even come as the design question in Kotlin if it is an old feature done a long time ago? You see, we are rewriting the compiler frontend based on the Kotlin specification which states the second behavior, even though the actual language has the first one. /5
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
This discrepancy was discovered a while ago during testing and was raised as a design question. During discussion, we've focused on the fact that "good" getters should not have side-effects, so calling getter once or twice does not matter, so let's change behavior to the spec. /6
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
Which one is "correct"? That is a really hard question. It depends on what you are trying to achieve. There is no apriori right answer. E.g., Kotlin does it in the first way (and returns 0), while C# does it in the second way (and returns -1). /4
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
So, there are two ways to desugar "--percent" expression on integers:
1: val upd = get() - 1; set(upd); get()
2: val upd = get() - 1; set(upd); upd
The first one calls property get/set/get and returns 0 in the example. The other calls get/set once and would return -1. /3
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
Two interacting features here are properties, which can have custom getters and setters, and pre-decrement/incremenet operators. In Kotiln, we define high-level features via "desugaring" into lower-level ones (sidenote: during compilation it is called "lowering"). /2
@relizarov ("Roman Elizarov") wrote:
Let me explain the story behind this poll. It recently came up as the Kotlin design question, and it is a great illustration of the tradeoffs in the language design and complexities that come up as different language features interact. /1
with quote tweet:
@relizarov ("Roman Elizarov") wrote:
This is not a trick question, just probing your programmer's intuition. Assume that you have a property that coerces its value in the setter:
var percent: Int = 0
set(value) { field = value.coerceIn(0, 100) }Don't run it! What should this line print?
println(--percent)
@meakoopa ("Anthony Oliveira") retweeted:
@StoicalSophist ("The Wreck of the Ella Fitzgerald") replied to a tweet by @kenklippenstein:
@kenklippenstein Oh, sure, leftists are all "be gay, do crime" until someone actually goes out and does it🙄
@meakoopa ("Anthony Oliveira") retweeted:
@KenJennings ("Ken Jennings") wrote:
If you don't like being compared to Weimar-era Nazis, you don't HAVE to ban drag cabaret.
@DSA_SanDiego ("DSA San Diego 🌴☀️") replied to a tweet by @DSA_SanDiego:
Let's keep pushing them! No Smart Streetlights, Invest in Our Community. Leave an e-comment and prepare to show-up in person on either March 22nd or April 27th, details to be released soon!
@DSA_SanDiego ("DSA San Diego 🌴☀️") wrote:
We've got one small win to share: SDPD is no longer bringing the Smart Streetlights to the first Privacy Advisory Board meeting!
@meakoopa ("Anthony Oliveira") retweeted:
@bobo_circus ("jessica ba'alba") wrote:
wtf i just heard my boyfriend's leitmotif & it's still incorporating elements from his ex's battle theme 😡😡😡
@meakoopa ("Anthony Oliveira") retweeted:
@take_japper ("ssj4 chicagoku") wrote:
quick question: can you name a commonly available public location in any given community that is: open after sundown; that teens can gather at without being charged money; and, won't lead to immediately being harassed by the cops. I honestly don't have an answer
with quote tweet:
@rex_woodbury ("Rex Woodbury") wrote:
Teens who meet up with their friends 'almost every day' is down from 50% in the 90s to 25% today.
Falls off a cliff around 2010, alongside the rise of smartphones and social media.