SpacemanDMM
SpacemanDMM copied to clipboard
A BYOND language smartness provider, map renderer, and more.
`#include` in a .dm file gives ``` unexpected token Punct(Less), expecting Token::String(path) path separated by '.', should be '/' got '>', expected one of: '/', '[', contents, newline, identifier ```
The TextMate grammar in the VSC extension sets scopes `entity.name.function.dm` and `meta.function.dm` for bare function calls `foo()`, but sets no particular scopes for method calls `bar.foo()`. It would be good...
For some reason, DMDoc is not properly catching the doc comments and applying them to the following item. Shows nothing on hover, if information is forced to display with control+hover,...
The ability to protect a var from **setting only** would be incredibly useful. For example, health values should never be directly written to by procs that aren't explicitly made for...
![image](https://user-images.githubusercontent.com/35135081/158113433-0cf96ac0-d245-494d-8a15-7a700330baf5.png)
Currently, we get "duplicate definition" errors from the parser when a file gets included multiple times, indicating that the file is actually being parsed at every `#include` of it, which...
See http://www.byond.com/forum/post/2750423 tl;dr BYOND doesn't throw a compiler error if you use a non-const in a switch range case (see code below) and instead silently uses `null` in place of...
According to the DMdoc readme: > //! Enclosing comments follow their item. However, when using this style, the VSCode extension does not display the comment in the mouse over menu...
SHOULD_NOT_SLEEP and SHOULD_BE_PURE have false positives based on incorrect inheritance assumptions
``` /proc/foo() SHOULD_NOT_SLEEP(TRUE) /datum/proc/foo() sleep(5) ``` `/datum/proc/foo()` will report that it has `SHOULD_NOT_SLEEP` set when it shouldn't.