Type Erasure in Scala -


i'm rather confused what's happening here:

import scala.collection.immutable._  object main extends app {   sealed trait node    sealed trait group    case class sheet(     val splat: string,     val charname: string,      val children: listmap[string, node],     val params0: listmap[string, param], //params0 separate sheet-general parameters      val note: option[note]     ) extends node group    case class attributes(val name: string) extends node group    case class param(val name: string, val value: string) extends node   case class note(val note: string) extends node

i've got 3 versions of replace function - last 1 one i'm trying write, others debugging.

  class sheetupdater(s: sheet) {         def replace1[t <: group](g: t): unit = {       s.children.head match {         case (_, _:sheet) =>         case (_, _:attributes) =>       }     }   }

this version throws no warnings, apparently have access type of s.children @ runtime.

  class sheetupdater(s: sheet) {     def replace2[t <: group](g: t): unit = {       g match {         case _:sheet =>         case _:attributes =>       }     }   }

neither version, apparently details of g's type also available @ runtime...

  class sheetupdater(s: sheet) {     def replace3[t <: group](g: t): unit = {       s.children.head match {         case (_, _:t) => //!         case (_, _:attributes) =>       }     }   }

... so, ends throwing me dreaded abstract type pattern t unchecked since eliminated erasure warning. what's going on here?

in scala, generics erased @ runtime, means runtime type of list[int] , list[boolean] same. because jvm whole erases generic types. due because jvm wanted remain backwards compatible way when generics first introduced...

there way around in scala using classtag, implicit parameter can threaded around whatever generic using.

you can think of : classtag passing type of generic argument. (it syntactic sugar passing implicit parameter of type classtag[t].)

import scala.reflect.classtag  class sheetupdater(s: sheet) {   def replace3[t <: group : classtag](g: t): unit = {     s.children.head match {       case (_, _:t) => //!       case (_, _:attributes) =>     }   } }

newer answers of question have more details.


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