Because the immutable interface exposes only the nonmutating methods of the underlying class, access to the object through the interface type preserves immutability. This allows you to use the immutable interface to prevent mutation. For example, the following code returns a reference to theMutableCirc...
Can you provide some details about the design decisions that went into it? Is it implemented inside the core props code or as an extra layer (e.g. an additional ref that is sync'ed with the props?) If it's an extra ref layer, does it exist always or is the component checking wheth...
I think we need to have understandable rules. So far I think "inherit REs unless output has its own build/host env" is relatively easy to explain (aside from checking the technical boxes from my POV), and a more complicated algorithm would need to provide a pretty big improvement in compa...
NOte that you'll probably loose lots of nice syntax checking, Intellisence and other stuff, so you'd better be sure that you do really, really need them... (See also: http://blogs.geekdojo.net/pdbartlett/archive/2004/02/23/1191.aspx where I first "owned up" to having had this ...
65 + name: build-${{ matrix.type }} 66 + container: 67 + image: matterlabs/llvm_runner:ubuntu20-llvm17-latest 68 + outputs: 69 + solc-version: ${{ steps.project_version.outputs.solc-version }} 70 + steps: 71 + 72 + - name: Checking out the Solidity repository 73 ...
Branching (i.e.ifstatements for you non-assembly people) can be a real performance killer. Only do branching if you need to for the correctness of an algorithm, or to save time on an expensive computation (e.g. checking a cache). ...