[Swift-user] Mapping question: how to map an optional file?

Mihael Hategan hategan at mcs.anl.gov
Tue Oct 26 18:09:51 CDT 2010


Right. I don't think we support optional data. I think that ties back
into the purely functional nature of swift.

I remember there being some discussion about this in the past, but I
don't think we reached any reasonable conclusion.

Mihael

On Tue, 2010-10-26 at 16:04 -0600, Michael Wilde wrote:
> Was: Re: mapping question
> 
> (relaying to swift-user to solicit additional thoughts)
> 
> Glen,
> 
> Offhand I dont see any alternative to the empty file. Ive had the same
> need in the past and dont see how to do it other than an empty file.
> Its almost like we need some way to represent a null file without the
> overhead of actually passing one. And some way to indicate when a null
> file is acceptable.
> 
> In your application would an empty file be problematic in performance
> or semantics?
> 
> - Mike
> 
> ----- "Glen Hocky" <hockyg at uchicago.edu> wrote: 
> > I'm trying to modify my swift scripts slightly so that one output
> file is optional. i know previously we had done something like map to
> an empty file but i'm having a hard time doing that without having my
> application create the empty file. Any suggestions? 
> 
> -- 
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
> 
> 
> _______________________________________________
> Swift-user mailing list
> Swift-user at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-user





More information about the Swift-user mailing list