[Swift-devel] Swift reference manual and syntax specification
Ben Clifford
benc at hawaga.org.uk
Mon Mar 11 04:33:33 CDT 2013
Yeah that looks pretty much like it. I guess I should've written it down
before then I could have had a paper...
Nice to see that someone else thinks my idea is not complete
crackheadedness, though.
One think that I like from 1987 is this, which is not to do with
parallel/hpc programming but has similar partial-ordered variables:
http://www.cs.ucla.edu/~stott/pop/
> There's been someone at Indiana working on semantics of monotonic variables, which is pretty much exactly
> what Ben described:
> http://www.cs.indiana.edu/~rrnewton/papers/2012-lambdapar-draft.pdf
>
> On Sun, Mar 10, 2013 at 6:46 PM, Ben Clifford <benc at hawaga.org.uk> wrote:
>
> > Your example is a good one, in that it (and probably several others)
> > would be needed to understand the topic of array closing. The current
> > Swift/T Guide says only "Arrays are part of Swift dataflow semantics. An
> > array is closed when all possible insertions to it are complete" but it
> > doesnt say how to understand that clause "...when all possible
> > insertions to it are complete", in particular what "all possible" means.
> > More examples are needed to understand it fully. Ideally, precise rules
> > and examples complement each other.
>
> wrt this, one approach to array closing that I had before was regarding
> the state of the array as constrained to move on a directed graph of
> states until they reach an end state (the closed state) - that gives not
> really a state machine, but perhaps something a bit like it, onto which
> maybe you could say "this kind of Swift code moves an array into this
> state". I never wrote that more formally, and I don't think it lines up
> entirely with the way that Swift does things, but it might be interesting
> to pursue.
>
> --
>
>
>
>
More information about the Swift-devel
mailing list