mastodon 4.7.3
I just completed "Rucksack Reorganization" - Day 3 - Advent of Code 2022 #AdventOfCode https://adventofcode.com/2022/day/3 again required some assistance, but Today is Saturday so we look tired - no photo!
I've completed "Camp Cleanup" - Day 4 - Advent of Code 2022 #AdventOfCode https://adventofcode.com/2022/day/4 Today I was I rest so I asked my assistant to solve the puzzle for me and with a little help from my side she did it!
I just completed "Rock Paper Scissors" - Day 2 - Advent of Code 2022 #AdventOfCode https://adventofcode.com/2022/day/2 without my assistant it'd be impossible!
I've completed Part One of "Calorie Counting" - Day 1 - Advent of Code 2022 #AdventOfCode https://adventofcode.com/2022/day/1
Google Gen AI SDK supports Python, JS/TS, Go, Java and .NET.
But not PHP.
The feature request for official PHP support is now assigned — Google Cloud says stars + real use cases help get it prioritized:
Hi everyone,
using Symfony Messenger I've noticed that I often have the need to route several Message types to different transports. Most often, when implementing CQRS, which of course could be solved by introducing a MarkerInterface, however, such use of the interface is considered in terms of bad practices and a code smell. That's why I decided to implement wildcards for the namespace. WDYT? https://github.com/symfony/symfony/pull/48531
@l3l0@phpc.social can we fix these links @heiglandreas@phpc.social
@edorian@phpc.social Thanks. Syntax is exactly where early feedback helps.
<...> was intentionally left available for future generics, since these are native
value types rather than generic class instances. {...} also keeps collection
literals visually distinct from arrays. But I agree the syntax is unfamiliar, so that trade-off is worth discussing.