Mirror of forum.nim-lang.org

2113 :: Compilation errors with strfmt 0.8.0

• axben (orginal) [2016-03-11T11:53:43+01:00] view original

  Compilation of

  echo "{:<10} {:<10} {:^10} {:>25}".fmt(1235,"Cat","Centered","Mouse")  # Just a sample
  Run

  fails with

  test.nim(7, 6) Error: type mismatch: got (string, int, tuple[typ: FmtType, precision: int, width: int, fill: nil, align: FmtAlign, sign: FmtSign, baseprefix: bool, upcase: bool, comma: bool, arysep: nil])
  but expected one of:
  strfmt.addformat(o: var Writer, x: T, fmt: Format)
  ...

  I'm using the latest(?) version of strfmt (0.8.0) and nim 0.13.1 as of today.

  What is the state of strfmt?

---

• rgv151 (orginal) [2016-03-11T11:58:58+01:00] view original

  I have a hot patch here: https://github.com/rgv151/strfmt/commit/7a9c6aadeb039a660d01f620967c713ede5106e3

---

• Varriount (orginal) [2016-03-11T12:03:27+01:00] view original

  So, is this a regression in concepts then? Or just a semantic change?

---

• Araq (orginal) [2016-03-13T08:26:18+01:00] view original

  A semantic change that we were aware of. Concepts are already hard enough to implement even without this "treat typedesc as value in the context of a concept" rule.

---