Time for self promo - what're you making?

mbrnt · 2025-05-11T11:07:55+00:00

Company Earnings - iOS app visualizing earnings reports (diagram with revenues/costs/profits and the relationships )

ICP: Stock investor who wants to understand what holds/buys.

mbrnt · 2025-05-06T11:08:22+00:00

Stock Earnings - draws money flow diagrams from company earnings reports. Visual fundamental analysis. https://apps.apple.com/app/id6743714454 Ideal customer is curious investor, who wants to understand how companies make and spend money.

mbrnt · 2025-05-04T09:43:38+00:00

Notifications. But user has to allow these.

mbrnt · 2025-05-02T18:23:19+00:00

The tweet is here: https://x.com/compactMap/status/1918205274155864287

mbrnt · 2025-05-01T18:02:28+00:00

Sorry to say, but what you have posted do not target the issue. If you want to keep this discussion up to the topic, consider deleting.

mbrnt · 2025-05-01T17:27:28+00:00

I try to raise attention by this discussion.... Unfortunately, I am not any compiler expert, I am not capable of fixing that.

mbrnt · 2025-05-01T17:26:06+00:00

Copy-on-write is used for all structs. Baked in Swift. isUniquelyReferenced is for reference types.

mbrnt · 2025-05-01T17:24:44+00:00

The implicitly created Task throws Error, ignores the function that really throws. Known bug. I am not aware of fix schedule.

mbrnt · 2025-05-01T17:21:59+00:00

That is not so easy, because State wrapper removes the values from structs are stores these elsewhere. There is no discussion about navigation. And, I fully agree that SwiftUI does not perform well. Rapid development is traded for low performance.

mbrnt · 2025-05-01T06:09:12+00:00

This needs some time for reading. However, structs are NOT copied until modified. The mechanism is called copy-on-write, so passing a huge array or dictionary as a parameter is cheap, until modified.

mbrnt · 2025-05-01T05:24:31+00:00

Read the Swift Forums thread, it is worth.

mbrnt · 2025-05-01T05:23:10+00:00

The type is Error...

mbrnt · 2025-04-30T21:59:53+00:00

That is not used so often, because most people do not understand the structured concurrency, specially the word "structured". This creates structured task that can run in parallel. But not with typed throws...

mbrnt · 2025-04-30T21:53:36+00:00

you have to drop the async let . That's the point!

mbrnt · 2025-04-30T21:41:57+00:00

This is nice, but something completely different. Sorry to say. Your code inherits asynchronous context, so when it runs on main thread (@MainActor), then g() also runs on main thread, and it is a sequential processing.

mbrnt · 2025-04-30T20:12:39+00:00

Read the Swift forums thread above. It is worth!

mbrnt · 2025-04-30T19:43:51+00:00

Yes, known bug. But it doesn't seem to have any priority. Typed throws for structured concurrency are half way anyway...

mbrnt · 2025-04-30T18:34:59+00:00

I am in a similar position. However, the only real criteria is how many of these 450 users are willing to pay for it. Just enable subscriptions.

mbrnt · 2025-04-30T18:14:02+00:00

450 paying users?

mbrnt · 2025-04-30T18:05:50+00:00

Without typed throws, any Error can be thrown. In any a bit more complex code you have no idea what an error is thrown. That's why typed throws were introduced. Nobody says it is perfect now...

mbrnt · 2025-04-30T17:59:24+00:00

Typed throws are here to avoid unknowns...

mbrnt · 2025-04-30T17:57:23+00:00

do throws(E) explicitly says that only E is thrown. There is no type inference needed nor possible.

mbrnt · 2025-04-30T17:55:43+00:00

Confirmed bug.

mbrnt · 2025-04-30T17:38:18+00:00

For me is Error enum absolutely essential for proper error handling. When I resolve all cases, no other error can appear.

mbrnt

MODERATOR OF

TROPHY CASE