I&#x27;m actually unsure how it works when making a derivative work like this, because the license has the following statement: &quot;Redistributions of source code must retain the above copyright notice, this
 list of conditions and the following disclaimer.&quot; Surely changing the name in the conditions would technically be changing the conditions themselves? Maybe I&#x27;m just worrying too much ;)

Nice API.Nitpick: you even ported the license from kiwi-java :-)&quot;Neither the name of kiwi-java nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.&quot;

I haven&#x27;t done any performance comparisons yet, unfortunately. I&#x27;m still working on improving the codebase to make it more Swifty. The backing fields are a leftover from the original Java implementation, and I didn&#x27;t want to change too much initially, but now I have a bunch of tests and am using it in another project (a PDF generation library), I will start to make these changes :)

Nice! Have you done any performance comparisons to C++ kiwi?Question: Any reason you manually added backing fields for properties instead of using private(set) var name: Type, for example? Since the latter has the effect of making it a let property outside of the class (cannot mutate an array exposed like this from the outside, for example).

Show HN: A pure Swift port of the Cassowary linear constraints solver