#37 Limitation: Encapsulated objects with exposed mutators can mutate

[pluresideas]

…te their state

Many thanks for your contribution, we truly appreciate it. We will appreciate it even more, if you make sure that you can say "YES" to each point in this short checklist:

• You made a small amount of changes (less than 100 lines, less than 10 files)
• You made changes related to only one bug (create separate PRs for separate problems)
• You are ready to defend your changes (there will be a code review)
• You don't touch what you don't understand
• You ran the build locally and it passed

This article will help you understand what we are looking for: http://www.yegor256.com/2015/02/09/serious-code-reviewer.html

Thank you for your contribution!

[0crat]

@yegor256/z everybody who has role REV is banned at #39; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #39; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #39; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #39; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[pluresideas]

@yegor256 I am not sure what the 0crat messages mean. Is anything else needed from my side?

[yegor256]

@pluresideas that's it, thanks!

[0crat]

Job gh:jcabi/jcabi-immutable#39 is not assigned, can't get performer