diff options
| author | 2025-02-27 17:19:23 -0500 | |
|---|---|---|
| committer | 2025-02-27 17:19:23 -0500 | |
| commit | 4a69b1db865e43719aa80d59a865ab6226d10465 (patch) | |
| tree | 16f25c4421ae5c5b0d930b206763ed507d7dacce | |
| parent | reorganize to remove subtype inheritance (diff) | |
replace comment about single dispatch and inheritance in README
| -rw-r--r-- | README.md | 5 |
1 files changed, 2 insertions, 3 deletions
@@ -20,9 +20,8 @@ surprises. ### Why Singly Polymorphic (aka Single Dispatch)? -Multiple dispatch is difficult in the presence of inheritance (in R6RS, -for instance). It would require either disambiguation or a method -resolution order, which are complicated. +Multiple dispatch runs into the problems that subtype inheritance runs +into (see the section "On Inheritance"). If one wanted multiple dispatch or multiple inheritance, it would be better to use a CLOS style system, which has much more fine-grained control over |
