Revision fc8ddcfbccb1d3da7fb81bf9a5f97e7797a7cd11 authored by Slava Pestov on 20 January 2016, 08:51:11 UTC, committed by Slava Pestov on 20 January 2016, 08:55:05 UTC
With an upcoming patch we would call setMutating() on materializeForSet before computing the setter's isMutating() in the case where a setter was explicitly declared 'nonmutating'. Fix that by replacing the setter->isMutating() call with a direct computation of the expected result. It seems that the materializeForSet of protocol protocol requirements has to be mutating, even if the protocol is a class protocol or the property is nonmutating -- I need to investigate why and fix SILGen to not make this assumption, but in the meantime, opt-out of the new logic with protocol requirements to avoid more breakage.
1 parent 1ba8f45
lit.cfg
import sys
import platform
# Let the main config do the real work.
lit_config.load_config(config,
os.path.join(os.path.dirname(os.path.dirname(__file__)), 'test', 'lit.cfg'))
# test_source_root: The root path where tests are located.
config.test_source_root = os.path.dirname(__file__)
Computing file changes ...