swift - Code runs fine on Playground; at the same time it yields an EXC_I386_GPFLT error -


i'm having curious issue in playground prints expected result @ same time see error telling me execution stopped because of exc_i386_gpflt error.

i'm using playground model how should api wrapper i'm writing used. idea of doing plan nice api future developers.

the following entire "planning" code have written plan out wrapper. feel free copy , paste on playground see problem in action:

class anilist {     init() {}      internal class userapis {         weak var parent: anilist? = nil          init(parent: anilist) {             self.parent = parent         }     }      lazy var user: userapis = { [unowned self] in         let userapi = userapis(parent: self)         return userapi     }() }  extension anilist.userapis {     func me(_ completionhandler: (results: [string]) -> void ) {         // logic, fetching stuff parent         completionhandler(results: ["lorem", "sammet"])     } }  let andy = anilist() andy.user.me { results in     print(results) }

curiously, prints ["lorem", "sammet"] properly, @ same time error.

successful error!

i have read (for c++) few other questions regarding error unfortunately haven't been able solve issue. can gather happening because i'm attempting access memory nil? in general, haven't been able find information regarding other being architecture protection.

while code runs fine, i'm hesitant putting on actual code yet, have no idea how behave. if works on first run, it's hard predict if produce errors in long run.

edit:

it looks has calculated lazy var. changing line this:

lazy var user: userapis = userapis(parent: self)

works expected (as in, prints array , doesn't give me exc_i386_gpflt error).

edit 2:

previous edit seems inaccurate information.

this isn't answer workaround till figure out why works:

let andy = anilist() let somevar = andy.user.me { results in     print(results) }

this gives compile time warning saying constant somevar inferred have type (), maybe unexpected.

but doing this:

let andy = anilist() let _ = andy.user.me { results     print(results) }

works fine without errors @ all. weird enough. it'd if explain why happens.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more