Re: Permanently sinking output ports

Well, the whole point is to let implementors do some basic optimization without requiring a full-blown *static* graph analysis. If a port has been discarded following the execution of the annotated p:sink but is later read it would issue a *dynamic* error.

That said, it was just a thought. It may well be that a static dependency graph analysis is not that costly to implement.

Romain.

On 17 nov. 2012, at 19:00, Alex Muir <alex.g.muir@gmail.com> wrote:

> I'm wondering if "hint" is the right word here. If the p:sink attribute is optional, the graph analysis program logic would be the same plus the addition of logic to handle the option. Wouldn't it have to be a "required" attribute to have some positive affect on graph analysis logic? 
>  
> 
> On Sat, Nov 17, 2012 at 11:48 AM, Romain Deltour <rdeltour@gmail.com> wrote:
> What I suggest is for the author to be able to give a hint to the implementation, so that it's easier to implement such optimization without requiring to perform a complete graph analysis.
> 
> 
> 
> -- 
> -
> 
> Alex G. Muir
> Software Engineering Consultant
> Linkedin Profile : http://ca.linkedin.com/pub/alex-muir/36/ab7/125
> Love African Kora Music? Take a moment to listen to Gambia's - Amadu Diabarte & Jali Bakary Konteh www.bafila.bandcamp.com Your support keeps Africa's griot tradition alive... Cheers!
>