David Hart

Im out of here. For those want to follow, I’m moving to Mastodon: spacekaren.sucks/xd3s6

"Le développement logiciel, c'est un peu comme les Lego, les possibilités sont infinies sauf qu'avec l'informatique nous ne sommes pas limités en nombre de briques." buff.ly/3u1N1St

@dimsumthinking Can’t wait for you to finish writing your bread book 😊

@dimsumthinking Should it stay at ambient temperature overnight? How do you “let it rise”?

@daveverwer Made me switch to Firefox

@pointfreeco Finished watching the Concise forms videos and really enjoyed them! But I'm having trouble using bindings because they don't seem to play great with scoped view states, that I started using for performance reasons. Any ideas?

@tonyarnold @TablePlus @gittower

Today is the day! Crafting Interpreters is available for purchase in print, Kindle, ebook, and PDF! Behold: craftinginterpreters.com It took a lot longer than I expected, but it's all done now. So long that I wrote a blog post about it: journal.stuffwithstuff.com/2021/07/29/640… 🎉📖🎉📖🎉📖🎉📖🎉

🪄 Et si en un claquement de doigts, on pouvait créer des #applications mobiles ! 📱Quelle serait l' #app que vous auriez envie de créer ? 👇 Partagez vos idées dans les commentaires !

@luka_bernardi Thanks, will do. Btw, what reasons should I go for a List over a LazyVStack if I don’t use any of the List specific APIs?

@dhartbit Currently you only have control over the visibility and color of it; but this is definitely good feedback to file.

List has gained a lot of new capabilities this year: - Swipe Actions - Pull-to-refresh (with `.refreshable(action:)`) - Separator customization Together with the new search API this will unlock so many more advanced use cases for your app. Try them out and send us your feedback

@icanzilb Really cool! Have you tried playing with Itterating AsyncSequence with for await instead of while/next?

@jckarter That’s the Xbox.

@groue That’s really smart! I always implemented those use cases with a key-value table. But that makes a lot of sense!

GRDB tip of the day: I wrote a guide for setting up "Singleton Records", aka "Single-Row Tables", which store configuration values, user preferences, and generally some global application state. This is a frequent need, and you may enjoy some guidance: github.com/groue/GRDB.swi…

I've spent the last few days battling bugs in the OS and frameworks, diligently opening bug reports with attached projects and simple reproducible cases. I feel worn down and depressed.

@kingatarthur @pathofshrines @beccadax @senderPath That's not the case here. We're talking about access to dynamic members from an extension of a @dynamicCallable type.

@dhartbit @pathofshrines @beccadax @senderPath It's discussed here: nshipster.com/callable/ "@​dynamicCallable and @​dynamicMemberLookup are declaration attributes, which means that they can’t be applied to existing declarations through an extension."

Is it me or is @dynamicMemberLookup broken inside extensions? bugs.swift.org/browse/SR-14284

@pathofshrines @slava_pestov @beccadax @senderPath Ah understood. Reminds me how I really like Ruby's prefix symbols to reference different scopes ($ for global, @ for instance, @@ for class). Explicit for the programmer, not too verbose, and great for the compiler 🙂

@slava_pestov @pathofshrines @beccadax @senderPath I got so used to never being explicit with self that I never thought of it as a workaround in this case!

@pathofshrines @slava_pestov @beccadax @senderPath Can someone help me understand the ambiguous case? With an example perhaps?

@slava_pestov @beccadax @pathofshrines @senderPath Yes, I'm only talking of the key path case.