diff options
author | Kartik Agaram <vc@akkartik.com> | 2020-08-03 21:45:41 -0700 |
---|---|---|
committer | Kartik Agaram <vc@akkartik.com> | 2020-08-03 21:45:41 -0700 |
commit | 208b28303cc2fa55939b06b5effac1cbd69d6356 (patch) | |
tree | c05d475ba5310718d8ccc9e85e59aecf8746021a /apps/mu | |
parent | 672ea33132c3e1870fa50661ded468b1da4f1794 (diff) | |
download | mu-208b28303cc2fa55939b06b5effac1cbd69d6356.tar.gz |
6715
There's a question of how we should match array types with a capacity on ones without. For now we're going to do the simplest possible thing and just make type-match? more robust. It'll always return false if the types don't match exactly. For ignoring capacity we'll rely on the checks of the `address` operation (which don't exist yet). This means we should do this to pass an address to an array to a function f with signature `f (addr array int)`: var a: (array int 3) var b/eax: (addr array int) <- address a f b rather than this: var a: (array int 3) var b/eax: (addr array int 3) <- address a f b Similar reasoning applies to stream types. Arrays and streams are currently the only types that can have an optional capacity.
Diffstat (limited to 'apps/mu')
-rwxr-xr-x | apps/mu | bin | 369145 -> 369174 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/apps/mu b/apps/mu
index 04eefef8..336596d1 100755
--- a/apps/mu
+++ b/apps/mu
Binary files differ |