John Estropia

859 posts

John Estropia

John Estropia

@JohnEstropia

iOS Engineer at @eureka_inc, Author of Swift lib CoreStore

Tokyo, Japan Katılım Eylül 2015
180 Takip Edilen395 Takipçiler
kishikawa katsumi 🍪
kishikawa katsumi 🍪@k_katsumi·
It is not well known what rules Swift Syntax follows to parse trivia. I added a trivia visualization feature to Swift AST Explorer. swift-ast-explorer.com This is useful for creating tools such as formatters or parsing documentation comments.
English
2
3
20
3.2K
John Estropia
John Estropia@JohnEstropia·
@onmyway133 @ChatJoyAI There’s been an influx of AI-related rejections this past few weeks. I’m assuming some guidelines (published or otherwise) had been updated recently
English
1
0
0
105
Khoa 🔥
Khoa 🔥@onmyway133·
AppStore rejection for @ChatJoyAI My app includes some default characters, like Doctor, which are not allowed since it makes it a medical app 🤖 "Your app provides medical diagnoses or treatment advice but does not include the required medical disclaimer" #iosdev #buildinpublic
Khoa 🔥 tweet media
English
15
2
41
16.6K
John Estropia
John Estropia@JohnEstropia·
@AMG4Z Thanks for your interest! I sent you a Twitter DM, but if you prefer to email instead you can also reach me from the support link available from within the VGCHelper app (About ->Feedback/Suggestions)
English
0
0
0
156
GOZEUS GT#
GOZEUS GT#@AMG4Z·
@JohnEstropia Nice. Can i DM to you? Facebook .... email or something. ( I can’t send massage on twitter )
English
1
0
0
21
John Estropia
John Estropia@JohnEstropia·
I wish there's a way to make #Xcode show different background colors/syntax highlighting between Result Builder closures, async closures, and standard closures
English
1
0
0
197
John Estropia
John Estropia@JohnEstropia·
@malhal The stack is limited by application memory (i.e. stack overflow) I’ve tackled this design problem before when I created type-safe schemas in github.com/JohnEstropia/C… Classes are still the most performant and practical. Value types can be interfaced afterwards using “snapshots”
English
0
0
0
28
Malcolm Hall
Malcolm Hall@malhal·
@JohnEstropia Structs are values on the memory stack, basically negligible compared to objects on the heap
English
1
0
0
23
John Estropia
John Estropia@JohnEstropia·
@malhal Fair enough, that’s how it’s done now anyway. But consider a query with thousands of fetched results. Because you are using structs objects would be loaded in memory all at once. Each time you pass that array you have a potential risk of blowing up memory with copies.
English
2
0
0
23
John Estropia
John Estropia@JohnEstropia·
@malhal Files don’t have the same complexity as ORMs. For example, structs cannot express inheritance nor relationships.
English
1
0
0
22
Malcolm Hall
Malcolm Hall@malhal·
@JohnEstropia It's good, it means persistence can be multi-threaded, it's how FileDocument works
English
1
0
0
28
John Estropia
John Estropia@JohnEstropia·
@malhal I disagree. Structs would be bad for observing persistent changes (since changing any property in a value type creates a new “instance”)
English
1
0
0
32
Malcolm Hall
Malcolm Hall@malhal·
@JohnEstropia It's not Swift standards, if it was the models would be structs. At least the predicates are structs though.
English
1
0
0
53