"Michael S. Tsirkin" writes:
> On Wed, Jun 15, 2016 at 10:41:48PM +0200, Markus Armbruster wrote:
>> Users of struct Range mess liberally with its members, which makes
>> refactoring hard. Create a set of methods, and convert all users to
>> call them instead of accessing members. The methods h
On Wed, Jun 15, 2016 at 10:41:48PM +0200, Markus Armbruster wrote:
> Users of struct Range mess liberally with its members, which makes
> refactoring hard. Create a set of methods, and convert all users to
> call them instead of accessing members. The methods have carefully
> worded contracts, an
Eric Blake writes:
> On 06/15/2016 02:41 PM, Markus Armbruster wrote:
>> Users of struct Range mess liberally with its members, which makes
>> refactoring hard. Create a set of methods, and convert all users to
>> call them instead of accessing members. The methods have carefully
>> worded cont
On 06/15/2016 02:41 PM, Markus Armbruster wrote:
> Users of struct Range mess liberally with its members, which makes
> refactoring hard. Create a set of methods, and convert all users to
> call them instead of accessing members. The methods have carefully
> worded contracts, and use assertions t
Users of struct Range mess liberally with its members, which makes
refactoring hard. Create a set of methods, and convert all users to
call them instead of accessing members. The methods have carefully
worded contracts, and use assertions to check them.
To help with tracking down the places that
