| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
fix #2335
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes `os.time` expected input is wrong #2235
|
|
Closes #2235
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Doc fix coroutine isyieldable
|
|
|
|
|
|
Add desc of skynet.task api
|
|
|
|
|
|
3rd: meta add bee
|
|
fix error
|
|
|
|
|
|
|
|
Co-authored-by: carsakiller <carsakiller@gmail.com>
|
|
All of these functions effectively call `tostring()`, when the passed parameter is a number. I think there is no need to raise warnings if users pass numbers instead of strings to these functions.
|
|
|
|
resolve #1942
|
|
meta: newproxy can accept a userdata value
|
|
This brings it in line with math.max, and max.min. This change allows the type inference to correctly infer the returned type if math.abs is passed an integer as an argument.
|
|
|
|
|
|
|
