--- !ditz.rubyforge.org,2008-03-06/issue 
title: "api: should duk_to_uint32(), duk_to_int32(), duk_to_uint16() use duk_(u)int_t return type?"
desc: |-
  Currently they return specific types duk_uint32_t, duk_int32_t, duk_uint16_t.
  These are not even the 'fast' variants which may require calling code to do
  sign/zero extensions and such.  Perhaps change the API to always use
  duk_int_t and duk_uint_t, it also simplifies caller type set?
type: :task
component: duk
release: v2.0
reporter: Sami Vaarala <sami.vaarala@iki.fi>
status: :unstarted
disposition: 
creation_time: 2014-06-10 12:24:38.074386 Z
references: []

id: aee28cd46229cc12aa9fd3f51aa5e6c435051904
log_events: 
- - 2014-06-10 12:24:38.218302 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-07-10 12:43:22.284036 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v0.12 from v0.11
  - ""
- - 2014-09-16 20:10:05.068237 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v1.1 from v0.12
  - ""
- - 2014-11-13 07:04:01.927741 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v2.0 from v1.1
  - ""