Smartphones manipulate our emotions and trigger our reflexes
Uncategorized
1
Posts
1
Posters
9
Views
-
Smartphones manipulate our emotions and trigger our reflexes
Link: https://theconversation.com/smartphones-manipulate-our-emotions-and-trigger-our-reflexes-no-wonder-were-addicted-265014
Discussion: https://news.ycombinator.com/item?id=45714348 -
undefined g3rt@mastodon.uno shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@riley @lesley the only way to avoid explicit casts is inheritance. Can you make foo inherit from both whatever you want it to inherit from AND bar? Or is multiple inheritance a no-no in your project?
-
@GustavinoBevilacqua @andrea_ferrero @ALFA
l'oro è circa 148€/grammo e ha un peso specifico di 19,32 g/cm³, quindi abbiamo un prezzo di ~2860€/cm³. Diciamo 3K€/cm³.
0.2 µm sono 2×10^-4 cm quindi abbiamo un costo* di ca. 60 centesimo al cm².
Non so quanto sia la superficie della visiera del casco di una tuta spaziale**, ma ipotizzando almeno 40×40 cm² = 1600 cm², mi vengono 960€.
*solo materia prima, esclusa la lavorazione
**men che meno gli occhiali dei VIP
-
#EmmanuelMacron: "Per essere liberi, bisogna essere temuti". Otto Paesi europei hanno accettato di partecipare al suo piano. Si tratta di Germania, Gran Bretagna, Polonia, Paesi Bassi, Belgio, Grecia, Svezia e Danimarca. L'Italia come sempre. La #Francia vuole rafforzare ed estendere la deterrenza nucleare - Internazionale https://www.internazionale.it/opinione/pierre-haski/2026/03/03/francia-deterrenza-nucleare
-
@lesley Also, I'd have to explicitly cast; the cast would not be invoked implicitly by the language.
-
@lesley Unfortunately, it's cumbersome to put struct bar first inside the struct foo; for reasons, I'd prefer struct foo to inherit from a third structure that puts some fields in its beginning, and struct bar can not inherit from it.
-
@NemoJmeno je ne l'ai absolument pas vu 😐
-
@jerzone we have had rain and melting temps for a week now. Trails are gone, just slush. Waiting for freezing temps so I can go and ride anywhere and everywhere.
-
@lesley yes, but in the case of @riley that's not the same issue: if foo has-a bar, there's no way to do the casting _implicitly_, as far as a I know. It would be possible with references by defining an implicit constructor of bar from foo, but this won't be applied to pointers.
The only work around I can think of is to define an overloaded function
bar * get_bar(bar * o) { return o; }
bar * get_bar(foo * o) { return &o->bar_element; }and wrap pointer arguments with that function.
