Suggestion: Lua Runtime Strictness #3119
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3119
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Runtime Strictness
https://content.minetest.net/packages/LMD/strictest/
Disallows questionable usage of the Lua API & Lua itself to help catch errors.
Description:
Runtime Strictness for Minetest Mods
Strictest consists of two components:
Particularly useful when writing new mods that don't target older Minetest versions.
when are these useful? lua is already rather strict, i can't recall a bug i blamed on such a feature.
the server generally runs the latest stable version, why should we care?
stuff that does shenanigans shouldn´t end up on the server so that mod wouldn´t be helpful there.
maybe useful in a dev environment but for me it would make more sense to add those things to luacheck or similar in your code editor to get a warning even before you start minetest.
(again, i need to not respond to things when i'm half asleep, i didn't properly understand this)
this is the sort of thing that ought to be run by developers in their local environment, not on a live server.
also, triggering errors for use of deprecated API is already a config option:
1c10988d6a/builtin/settingtypes.txt (L1583-L1587)
however, your-land depends on a lot of mods which haven't seen active development in a long time, and use deprecated API calls. cleaning all that up is something i've had in the back of my head for a while, but there's been more important things to care about.
This is basically a question how to deal with depreciation messages in abandoned upstream mods.