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
doxygen.header
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html><head>
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
<meta name="keywords" content="Swift,Low Level Virtual Machine,C++,doxygen,API,documentation"/>
<meta name="description" content="C++ source code API documentation for Swift."/>
<title>Swift: $title</title>
<link href="doxygen.css" rel="stylesheet" type="text/css"/>
</head><body>
<p class="title">Swift API Documentation</p>
Computing file changes ...
