You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comments of the V method are formatted a certain way and the attempt the pop-up help fails to parse the way you may expect
Expected Behavior
Cleanly formatted pop-up help
Current Behavior
At the arrow tip the first bullet of the comment is not in the dark gray box the parser is grabbing the next line and putting it next to the Attributes comment.
Reproduction Steps
Paste in the comments for a given struct and hold your mouse over the struct name.
Possible Solution
No response
Additional Information/Context
No response
Environment details (v doctor output)
PS S:\> v doctor
V full version: V 0.4.9 45fd7eb.fdf0c0f
OS: windows, Microsoft Windows 11 Pro v26100 64-bit
Processor: 24 cpus, 64bit, little endian,
getwd: S:\
vexe: S:\repo\vlang\v.exe
vexe mtime: 2024-12-26 12:37:10
vroot: OK, value: S:\repo\vlang
VMODULES: OK, value: C:\Users\john3\.vmodules
VTMP: OK, value: C:\Users\john3\AppData\Local\Temp\v_0
Git version: git version 2.45.1.windows.1
Git vroot status: 0.4.9-41-gfdf0c0f0 (2 commit(s) behind V master)
.git/config present: true
CC version: Error: 'cc' is not recognized as an internal or external command,
operable program or batch file.
emcc version: Error: 'emcc' is not recognized as an internal or external command,
operable program or batch file.
thirdparty/tcc status: thirdparty-windows-amd64 b425ac82
IDE Type (IDEA Community/Ultimate, GoLand, CLion, etc.)
CLion 2024.3.1.1
Build #CL-243.22562.225, built on December 18, 2024
Licensed to Richard Wheeler
Subscription is active until December 15, 2025.
Runtime version: 21.0.5+8-b631.28 amd64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
.NET Core v8.0.4 x64 (Server GC)
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2048M
Cores: 24
Registry:
actionSystem.update.actions.warn.dataRules.on.edt=false
debugger.new.tool.window.layout=true
debugger.attach.dialog.enabled=true
run.processes.with.pty=TRUE
ide.experimental.ui=true
ide.slow.operations.assertion=false
cache.folding.model.on.disk=false
i18n.locale=
llm.show.ai.promotion.window.on.start=false
terminal.new.ui=true
Non-Bundled Plugins:
Batch Scripts Support (1.0.13)
com.jetbrains.space (243.21565.122)
io.vlang (2024.3.1)
Plugin Version
2024.3.1
The text was updated successfully, but these errors were encountered:
Describe the bug
Comments of the V method are formatted a certain way and the attempt the pop-up help fails to parse the way you may expect
Expected Behavior
Cleanly formatted pop-up help
Current Behavior
At the arrow tip the first bullet of the comment is not in the dark gray box the parser is grabbing the next line and putting it next to the Attributes comment.
Reproduction Steps
Paste in the comments for a given struct and hold your mouse over the struct name.
Possible Solution
No response
Additional Information/Context
No response
Environment details (
v doctor
output)IDE Type (IDEA Community/Ultimate, GoLand, CLion, etc.)
CLion 2024.3.1.1
Build #CL-243.22562.225, built on December 18, 2024
Licensed to Richard Wheeler
Subscription is active until December 15, 2025.
Runtime version: 21.0.5+8-b631.28 amd64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
.NET Core v8.0.4 x64 (Server GC)
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2048M
Cores: 24
Registry:
actionSystem.update.actions.warn.dataRules.on.edt=false
debugger.new.tool.window.layout=true
debugger.attach.dialog.enabled=true
run.processes.with.pty=TRUE
ide.experimental.ui=true
ide.slow.operations.assertion=false
cache.folding.model.on.disk=false
i18n.locale=
llm.show.ai.promotion.window.on.start=false
terminal.new.ui=true
Non-Bundled Plugins:
Batch Scripts Support (1.0.13)
com.jetbrains.space (243.21565.122)
io.vlang (2024.3.1)
Plugin Version
2024.3.1
The text was updated successfully, but these errors were encountered: