[swift-dev] Exclusivity checker hacking?

[David Zarzycki]

> On Oct 5, 2017, at 16:50, Michael Gottesman via swift-dev <swift-dev at swift.org> wrote:
> 
> 
>> On Oct 5, 2017, at 1:42 PM, David Zarzycki via swift-dev <swift-dev at swift.org> wrote:
>> 
>> Hello,
>> 
>> As an experiment, I’d like to force the exclusivity checking logic to always error at compile time, rather than a mix of compile time and run time. Near as I can tell, there is no built in debugging logic to do this (not even to warn when dynamic checks are added). Am I missing something? Where would be the best place in the code to make the dynamic checker error/warning at compile time? Would a warning be useful to others? Or should I just keep this on a throwaway branch?
> 
> Dave, what exactly are you trying to do?

Hi Michael,

I’m trying to understand the exclusivity model in practice and I’m finding that auditing the SIL/assembly output for dynamic checks is a kind of pain.

> 
> At some point, I plan on adding static checking for exclusivity like the ownership model. I imagine we could just error whenever we can not eliminate a runtime check. Would that solve your problem?

To be clear, the “problem” I’m solving is my own curiosity. Ultimately, I was just looking for some hints on where I could hack in some code to warn/note when checks are generated and error when SIL cannot eliminate dynamic checks.

Thanks,
Dave


> 
>> 
>> Thanks,
>> Dave
>> _______________________________________________
>> swift-dev mailing list
>> swift-dev at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-dev
> 
> _______________________________________________
> swift-dev mailing list
> swift-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev