A place for developers to talk about building on Farcaster.

/dev

I still don't know how I feel about Typescript type definition "magic".

It sort of feels a bit like C++ macros.

I guess it just takes getting used to them.

These are a big contrast with Go which is such a barebones language although I do love struct field tags and reflection.

They also recently introduced genetics which I haven't used much yet.

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

Arguably go's generics aren't "real" generics anyway, they're missing out on a lot of what can make them a powerful language feature, so you're not missing much by not using them, usually.

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

One of the most expressive aspects of generics is how it enables a more ergonomic way to declare the transformation of types. Unfortunately, the critical piece, that receiver methods cannot use a generic type parameter different from the receiver's type parameters means a lot of workarounds are needed.

One of the most expressive aspects of generics is how it enables a more ergonomic way to declare the transformation of types. Unfortunately, the critical piece, that receiver methods cannot use a generic type parameter different from the receiver's type parameters means a lot of workarounds are needed.

https://dev.to/chrismwendt/limitations-of-go-generics-5834

In what way are they not "real" generics?
What are they missing?

Each language has different capabilities with genetics but the foundation is compile-time type checks and constraints right?