Is there a way to constrain (generic) type parameters?
php editor Youzi discussed a common question: Is there a way to constrain (general) type parameters? In PHP, we often need to impose type constraints on the parameters of functions or methods to ensure that the parameters passed in meet specific type requirements. However, there is currently no direct way to constrain generic type parameters, such as arrays or objects. However, we can implement constraints on common type parameters by writing more strict type checking logic to ensure the correctness and consistency of the parameters. In this article, we'll explore several ways to implement generic type parameter constraints, as well as their pros and cons.
Question content
I just started learning generics. So I'm trying to generalize a driver for a custom database that runs on some protobuf messages.
I would like to find a way to further constrain my generic type, but as a pointer, i.e. make sure (tell the compiler) that the constraint e implements another method.
First, I limited the entities that the database can handle.
type entity interface { pb.msga | pb.msgb | pb.msgc }
Then, a common interface describing the functionality of the database was written so that it could be used by different services handling their own raw messages:
type db[e entity] interface { get(...) (e, error) list(...) ([]e, error) ... }
So far so good. However, I also want to (de)serialize these entities when communicating with the database so that they can be sent over the network, cloned and merged. Something like this:
func encode[e entity](v *e) ([]byte, error) { return proto.marshal(v) }
However, the above code gives the following error:
cannot use val (variable of type *e) as type protoreflect.protomessage in argument to proto.marshal: *e does not implement protoreflect.protomessage (type *e is pointer to type parameter, not type parameter)
The problem is that proto.marshal
requires entities (*e) to implement the proto.message
interface, i.e. the protoreflect()
method, for all my entity types Both implement the method, but it is unconstrained and cannot be inferred by the compiler.
I also tried defining the entity as:
type Entity interface { *pb.MsgA | *pb.MsgB | *pb.MsgC proto.Message }
However, this doesn't feel right, besides the fact that I need to do some extra protreflect operations to instantiate the proto.messages referenced by the entity pointer.
Solution
You can do this:
func encode[m interface { *e; proto.message }, e entity](v m) ([]byte, error) { return proto.marshal(v) }
If you want a more concise syntax than the above, you can cancel the message constraint:
type Message[E Entity] interface { *E proto.Message } func Encode[M Message[E], E Entity](v M) ([]byte, error) { return proto.Marshal(v) }
https://www.php.cn/link/20ba66f905957b34253d9d7abde919f3
The above is the detailed content of Is there a way to constrain (generic) type parameters?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

This article explains Go's package import mechanisms: named imports (e.g., import "fmt") and blank imports (e.g., import _ "fmt"). Named imports make package contents accessible, while blank imports only execute t

This article explains Beego's NewFlash() function for inter-page data transfer in web applications. It focuses on using NewFlash() to display temporary messages (success, error, warning) between controllers, leveraging the session mechanism. Limita

This article details efficient conversion of MySQL query results into Go struct slices. It emphasizes using database/sql's Scan method for optimal performance, avoiding manual parsing. Best practices for struct field mapping using db tags and robus

This article explores Go's custom type constraints for generics. It details how interfaces define minimum type requirements for generic functions, improving type safety and code reusability. The article also discusses limitations and best practices

This article demonstrates creating mocks and stubs in Go for unit testing. It emphasizes using interfaces, provides examples of mock implementations, and discusses best practices like keeping mocks focused and using assertion libraries. The articl

This article details efficient file writing in Go, comparing os.WriteFile (suitable for small files) with os.OpenFile and buffered writes (optimal for large files). It emphasizes robust error handling, using defer, and checking for specific errors.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

This article explores using tracing tools to analyze Go application execution flow. It discusses manual and automatic instrumentation techniques, comparing tools like Jaeger, Zipkin, and OpenTelemetry, and highlighting effective data visualization
