Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFix signature of JS_BufferIsCompilableUnit #192
Conversation
| *mut JSContext, | ||
| obj: | ||
| Handle<*mut JSObject>, | ||
| utf8: | ||
| *const i8, | ||
| length: | ||
| u32) | ||
| u64) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
tschneidereit
Aug 20, 2015
Author
Contributor
This is size_t. Should we be be using usize?
Probably, yes. It seems like bindgen generated wrong code for size_t? I
wonder if that afflicts more sites than just this one.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Manishearth
Aug 20, 2015
Member
Is libc::size_t different from usize? It would be nice to use Rust ints whenever possible.
|
https://gist.github.com/michaelwu/a9525f07112a8224a540 is the latest output from bindgen. Replacing |
This comment has been minimized.
This comment has been minimized.
michaelwu
commented on src/jsapi.rs in 4211969
Aug 20, 2015
|
This needs to be |
This comment has been minimized.
This comment has been minimized.
michaelwu
commented on src/jsapi.rs in 4211969
Aug 20, 2015
|
Shouldn't work everywhere. Since this is using size_t, this particular symbol likely to be mangled in three different ways. One for 32bit systems, one for 64 bit Linux, and another for 64 bit OSX. This is why many functions that use size_t have three different versions, controlled by cfg attributes. |
|
This should be fixed by the bindings update. |
|
#198 will fix this. |
tschneidereit commentedAug 20, 2015
r? @larsbergstrom