Changelog
*Sourced from [rlua's changelog](https://github.com/kyren/rlua/blob/master/CHANGELOG.md).*
> ## [0.16.1]
> - Documentation fixes
>
> ## [0.16]
> - Small fixes for the way new `Lua` states are created, preventing some potential unhandled errors
> - Propery mark all internal panics as internal and indicative of a bug
> - HUGE API incompatible change: move most of the `Lua` API into `Context` and require context
> callbacks to generate a branding lifetime, and use this branding lifetime on handle types. Fixes
> a hard to trigger soundness issue, and removes the only remaining API panic (that is not a bug).
> See the documentation for the `Lua` type for more details.
> - Fix `error_traceback` to work in all cases (thanks [**yasumutte**](https://github.com/yasumutte)!)
> - Use compiletest_rs on stable
> - API incompatible change: Change to use 2018 edition, `rlua` now requires rustc 1.31 to use.
> - Implement `ToLua` for `CStr` and `CString`, implement `FromLua` for `CString` (thanks [**althonos**](https://github.com/althonos)!)
> - Add ability to control what std libraries are loaded in a Lua state on startup
> (huge thanks to [**Shiroy**](https://github.com/Shiroy)!)
> - Add ability to set the Lua "hook function", which allows for limiting the execution of running scripts
> (huge thanks to [**lemarcuspoilus**](https://github.com/lemarcuspoilus)!)
> - API incompatible change: remove `failure` as a dependency, `Error` no longer implements
> `failure::Fail`.
> - API incompatible change: change the API for loading Lua chunks to allow for changing _ENV.
> `Context::load` now returns a builder on which you can set the chunk name and _ENV.
> - API incompatible change: remove `str` assumptions from the remaining places: the `UserData` trait
> and named registry keys
> - (Painstakingly!) remove the need for the `gc_guard` garbage collector hack, and thus also the
> "abort on OOM" hack.
> - Add an API for memory limits, now possible because of removal of `gc_guard`.
> - Add an API for controlling the garbage collector, also now possible due to the removal of `gc_guard`.
> - Remove the last internal aborts from `rlua`, possible to make safe due to the removal of `gc_guard`.
Commits
- [`32062c2`](https://github.com/kyren/rlua/commit/32062c2786e24797ab960e7ab074dfa1e935cfaa) (cargo-release) version 0.16.1
- [`54be367`](https://github.com/kyren/rlua/commit/54be36751115e9ae3351519d30a2389ed73f99d3) Update changelog for docfix update
- [`0c77fef`](https://github.com/kyren/rlua/commit/0c77fef222ad2d1a2cfbbefbfc730c879de71f28) Change `RegistryKey` docs to explain in terms of `Lua::context` instead
- [`26f78bd`](https://github.com/kyren/rlua/commit/26f78bd0d1c74e3632737957bbea1082bad9b3d0) Be consistent with backtick quoting
- [`ebdc134`](https://github.com/kyren/rlua/commit/ebdc1341d235a1851989b4eabfdc4a2df84c49ea) Remove incorrect doc comment from `gc_step`
- [`b2d2232`](https://github.com/kyren/rlua/commit/b2d22328b6be11615877a1f3d6bda998a06ad4f0) Fix documentation on `Lua::context`
- [`3bb89b4`](https://github.com/kyren/rlua/commit/3bb89b4928d759f1f6b0bd03b14a5a8d1bbf70c4) Slightly clarify that I mean panics in user code, not panics in rlua triggere...
- [`e8ab7aa`](https://github.com/kyren/rlua/commit/e8ab7aace7841898a36fe0f76df761da000d84b4) (cargo-release) start next development iteration 0.16.1-alpha.0
- [`78b6db8`](https://github.com/kyren/rlua/commit/78b6db804cf90c8c52e0d84a8405e5d4fb650a4c) (cargo-release) version 0.16.0
- [`c30727d`](https://github.com/kyren/rlua/commit/c30727dbff8b10c7e639cd91d8689f5be484a147) README editing
- Additional commits viewable in [compare view](https://github.com/chucklefish/rlua/compare/0.15.3...0.16.1)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking Bump now in your Dependabot dashboard.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Bumps rlua from 0.15.3 to 0.16.1.
Changelog
*Sourced from [rlua's changelog](https://github.com/kyren/rlua/blob/master/CHANGELOG.md).* > ## [0.16.1] > - Documentation fixes > > ## [0.16] > - Small fixes for the way new `Lua` states are created, preventing some potential unhandled errors > - Propery mark all internal panics as internal and indicative of a bug > - HUGE API incompatible change: move most of the `Lua` API into `Context` and require context > callbacks to generate a branding lifetime, and use this branding lifetime on handle types. Fixes > a hard to trigger soundness issue, and removes the only remaining API panic (that is not a bug). > See the documentation for the `Lua` type for more details. > - Fix `error_traceback` to work in all cases (thanks [**yasumutte**](https://github.com/yasumutte)!) > - Use compiletest_rs on stable > - API incompatible change: Change to use 2018 edition, `rlua` now requires rustc 1.31 to use. > - Implement `ToLua` for `CStr` and `CString`, implement `FromLua` for `CString` (thanks [**althonos**](https://github.com/althonos)!) > - Add ability to control what std libraries are loaded in a Lua state on startup > (huge thanks to [**Shiroy**](https://github.com/Shiroy)!) > - Add ability to set the Lua "hook function", which allows for limiting the execution of running scripts > (huge thanks to [**lemarcuspoilus**](https://github.com/lemarcuspoilus)!) > - API incompatible change: remove `failure` as a dependency, `Error` no longer implements > `failure::Fail`. > - API incompatible change: change the API for loading Lua chunks to allow for changing _ENV. > `Context::load` now returns a builder on which you can set the chunk name and _ENV. > - API incompatible change: remove `str` assumptions from the remaining places: the `UserData` trait > and named registry keys > - (Painstakingly!) remove the need for the `gc_guard` garbage collector hack, and thus also the > "abort on OOM" hack. > - Add an API for memory limits, now possible because of removal of `gc_guard`. > - Add an API for controlling the garbage collector, also now possible due to the removal of `gc_guard`. > - Remove the last internal aborts from `rlua`, possible to make safe due to the removal of `gc_guard`.Commits
- [`32062c2`](https://github.com/kyren/rlua/commit/32062c2786e24797ab960e7ab074dfa1e935cfaa) (cargo-release) version 0.16.1 - [`54be367`](https://github.com/kyren/rlua/commit/54be36751115e9ae3351519d30a2389ed73f99d3) Update changelog for docfix update - [`0c77fef`](https://github.com/kyren/rlua/commit/0c77fef222ad2d1a2cfbbefbfc730c879de71f28) Change `RegistryKey` docs to explain in terms of `Lua::context` instead - [`26f78bd`](https://github.com/kyren/rlua/commit/26f78bd0d1c74e3632737957bbea1082bad9b3d0) Be consistent with backtick quoting - [`ebdc134`](https://github.com/kyren/rlua/commit/ebdc1341d235a1851989b4eabfdc4a2df84c49ea) Remove incorrect doc comment from `gc_step` - [`b2d2232`](https://github.com/kyren/rlua/commit/b2d22328b6be11615877a1f3d6bda998a06ad4f0) Fix documentation on `Lua::context` - [`3bb89b4`](https://github.com/kyren/rlua/commit/3bb89b4928d759f1f6b0bd03b14a5a8d1bbf70c4) Slightly clarify that I mean panics in user code, not panics in rlua triggere... - [`e8ab7aa`](https://github.com/kyren/rlua/commit/e8ab7aace7841898a36fe0f76df761da000d84b4) (cargo-release) start next development iteration 0.16.1-alpha.0 - [`78b6db8`](https://github.com/kyren/rlua/commit/78b6db804cf90c8c52e0d84a8405e5d4fb650a4c) (cargo-release) version 0.16.0 - [`c30727d`](https://github.com/kyren/rlua/commit/c30727dbff8b10c7e639cd91d8689f5be484a147) README editing - Additional commits viewable in [compare view](https://github.com/chucklefish/rlua/compare/0.15.3...0.16.1)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking
Bump nowin your Dependabot dashboard.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.