@Lensflare haha, thx for the research and explanation, it makes sense. TIL! (not sure if it is the beauty of swift tho haha)

where are the swift fanboys? should i read protocol oriented programming again?

@Lensflare sorry if you look into the IE case, it is actually object referenced closure that referenced upper scope variable that referenced back to the object. the chain sometime can goes very long.

@spongessuck thanks for the advice, i'd rather abandon the whole apple ship completely and code in kotlin/java with tracing GC happily forever.

@lorentz what's even worse is, once you've done the explicit init(), because the swift language will stop creating the implicity init() for you, so starting from now you are responsible for making sure the params in `init(...params) ` is always up-to-date with every changes of public properties defined in the struct. combined with no tracing GC and only ARC, i had a feeling that I merely a miserable robot that keep doing meaningless repetitions as instructed by genius apple engineers.

@Lensflare thanks for the input. IMO a programming language that requires human to be "careful" in an area that the defects are very difficult to be spotted is not a good programming language, no matter how good the performance is. You know what it reminds me? It reminds me Internet Explorer <= 7 if you still remember the name. Back in the time it was using ARC and it was notoriously famous for it's leaking issue caused by closure having a reference to a dom in parent scope and that dom's onXXXX somehow referenced back to the closure.

@lorentz the longer story is, if you don't explicitly specify a init(), they will by default create one implicitly for you, that default one has "internal" modifier, meaning that will be accessible from within the same project. not sure if this is what you want as my understanding is that you want it actually to be `private`. This default init() is actually quite convenient, it allows you to initialise all the none private properties as init parameters. but the trouble is, because the default `internal` modifier, there is NO way to expose the implicit default init() to external project, hence you will have to manually repeatitively creating the init() explicitly for each struct you want to expose to external project, even tho you've already gave it a modifier 'public'.

@ElectroArchiver or did i misunderstand what you trying to express?

@ElectroArchiver didn't see this msg sorry for late reply, but are you sure that string has slice() method? are you sure you are not using an extension? or are you sure you talking about swift?

I did some searches there is no such slice() method came up:

https://dev.to/bibinjaimon/...

https://stackoverflow.com/questions...

@M3m35terJ05h how can that be blunt if you are using somebody else's hook which changed the internal of state object, and 90% of the time it works without problem, and 10% of the time react moans about it by behaving weirdly in some the other places that has nothing todo with the place where you used the hook?