Mirror of forum.nim-lang.org

7047 :: Avoid adding `m_type` field in JS Objects?

• r3c (orginal) [2020-11-07T12:31:13+01:00] view original

  Lets say we have

  type User = object
    name: cstring
    id: cstring
  Run

  if we do

  
  var user: User
  user.name = "Somename"
  user.id = "Someid"
  Run

  The resulting JS code is

  
  var user = {[name:  "Somename", id: "Someid"]}
  Run

  but if we initialize it directly like

  var user = User(name:  "Somename", id: "Someid")
  Run

  The resulting JS code is

  
  var user = {[name:  "Somename", id: "Someid", m_type: NIT80354703475]}
  Run

  this is with -d:release and -d:danger, and when you have nested objects its very annoying

  Is there any switch to turn the type info off?

---

• lotzz (orginal) [2020-11-07T19:04:54+01:00] view original

  Could it be because you didn't explicitly define the type of user in the object initialization example? I don't have my computer with me or id have a more definite answer

---

• DeletedUser (orginal) [2020-11-07T21:31:37+01:00] view original

  You can use the {} macro from jsffi to turn it directly to a JS object. You would just do User{name: "Somename", id: "Someid"}.

---

• r3c (orginal) [2020-11-07T22:10:40+01:00] view original

  Tnx, it worked!

  Still, this is a workaround, the good thing about Nim when compiling to JS is that you can use the types, but i still dont see why this extra typeinfo is added, the size of the output could be reduced by half if it wasn't this m_type. Who needs it anyway :)))

---