| | 5 | |
| | 6 | == Why == |
| | 7 | |
| | 8 | from #parrotsketch: |
| | 9 | {{{ |
| | 10 | cotto> allison, what's your reason for deprecating the PMC UnionVal? |
| | 11 | (I can see some reasons of my own, I'm just curious what you see.) |
| | 12 | chromatic> It's typeunsafe and it's a premature optimization. |
| | 13 | chromatic> It makes PIR-level subclassing Very Difficult. |
| | 14 | allison> cotto: it prevents subclassing, for one (because the child may be trying to use the union val differently) |
| | 15 | cotto> thanks. eoq |
| | 16 | allison> cotto: and just generally dangerous, to be using blobs of memory like that |
| | 17 | chromatic> It violates encapsulation. |
| | 18 | allison> chromatic: yes, those too |
| | 19 | NotFound> And it increases coupling between pmcs |
| | 20 | allison> cotto: it also bloats the PMC header structure |
| | 21 | }}} |
