© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
Reasons for Using Interfaces and Prototypes Over Classes in Effect Data Types - Effect Community
EC
Effect Community
•
12mo ago
jvliwanag
Reasons for Using Interfaces and Prototypes Over Classes in Effect Data Types
hi
, might there be good references to why effect data types
(e
.g
. HashMap
) are written as such
? I mean declaring an interface
, then creating a Proto object then having a
makeImpl
makeImpl
to tie it together
. Curious why not just regular
class
class
?
Effect Community
Join
Production-grade applications in TypeScript.
6,221
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Recent Announcements
Similar Threads
Was this page helpful?
Yes
No
Similar Threads
Using interfaces instead of classes for tagged errors in Effect: Pros and Cons
EC
Effect Community / 🚀-beginners
8mo ago
Converting TypeScript Types to Schema for Effect and Data Parsing
EC
Effect Community / 🚀-beginners
2mo ago
Using Functions vs Interfaces in Effect for Context Management Services
EC
Effect Community / 🚀-beginners
3y ago
Using Queue and Retry for Data Migration in Effect
EC
Effect Community / 🚀-beginners
6mo ago