@Araq \- thanks for the precision - I'll focus on using gc:arc on latency and
memory-sensitive applications.
Hi
is \--gc:arc considered ready for production use in nim 1.2? I notice
considerably worse performance of some code compiled using \--gc:arc. Here's an
example:
import times, strutils
type
OpType = enum Inc, Move, Loop, Print
Ops = seq[Op]
Op = object
Running nimble test under Linux with nim version 1.0.6 yields messages such as
Key 8205 in SharedTable with value 8205 but missing from StashTable
Key 14365 in SharedTable with value 14365 but missing from StashTable
Key 8205 in SharedTable with value 8205 but missing from
Hi cdunn
change your strlen wrapper in raptor_db.nim to
proc strlen(a: var Headroom): int =
let n = strlen(cast[cstring](a[0].addr))
echo " calc'd:", n
return n
Run
You'll then get an assertion error in t_raptor_db.nim:
:
There is an overload to instantRows which takes a var seq[DbColumn] as in
iterator instantRows*(db: DbConn; columns: var DbColumns; query: SqlQuery;
args: varargs[string, `$`]): InstantRow =
Run
So you should be able to do something like:
Judging from the c example you posted, your sizes are wrong. On my system utmpx
is defined something like
utmpx* = object
ut_type*:ut_type # Type of record
ut_pid*:cint # PID of login process
I view Nim as a wolf: cunning, sneaky, shy and yet loyal
Just to chime in on this: I see nothing wrong per se with TMTOWTDI
(theres-more-than-one-way-to-do-it) but a syntax skin is a hard sell
considering the main priority should be getting that v1.0 release out now. I'm
a fan of the principle of least surprise - programming is hard enough to get
