[FEATURE]: 考虑调用变量不需要前缀$

[azhz1107cat]

📋 Feature Request

Please provide a brief description of the feature you would like to see.

var x=100;
MagBox x;

---

✅ Is your feature request related to a problem?

Please describe the problem you are trying to solve with this feature.

---

💡 Describe the solution you'd like

A clear and concise description of what you want to happen.

---

🔧 Describe alternatives you've considered

Have you considered any alternative solutions or features?

---

📷 Screenshots

If applicable, add any mockups, screenshots, or diagrams that could help explain your feature request.

---

🧑‍💻 Environment

If the feature is platform-dependent, please specify:

• OS: [e.g., Windows 10 / macOS Big Sur / Ubuntu 20.04]
• Version: [e.g., v1.2.3]

---

🔧 Additional context

Any additional information or context that might help in implementing this feature.

[Ansurfen]

因为Hulo的命令类型是基础数据类型，如果没有前缀，就无法区分变量和命令。例如下面这段代码，没有前缀就无法区分 net 到底是变量还是子命令：

fn test_at() {
    at "marketing";
    at "corp" 3;
    at "corp" "8:00" -i net share reports "marketing\\reports" >> "maintenance\\reports\\corp.txt";
    at "marketing" "00:00" --every [5, 10, 15, 20, 25, 30] archive;
    at --delete;
}

[Ansurfen]

感谢你的反馈，现在Hulo的更新内容可能会暂时搁置了，我目前在开发另一个项目 opencmd —— 用Hulo的代码声明式描述命令，我会先将这套系统建立出来，开发出类似的SDK、manpage生成、md文档、类似swagger的命令schema等工具链，在继续开发Hulo编程语言，上面的代码片段也是来源于这个项目： https://github.com/opencommand/commands/blob/main/a/at.hl

[azhz1107cat]

因为Hulo的命令类型是基础数据类型，如果没有前缀，就无法区分变量和命令。例如下面这段代码，没有前缀就无法区分 net 到底是变量还是子命令：

fn test_at() {
    at "marketing";
    at "corp" 3;
    at "corp" "8:00" -i net share reports "marketing\\reports" >> "maintenance\\reports\\corp.txt";
    at "marketing" "00:00" --every [5, 10, 15, 20, 25, 30] archive;
    at --delete;
}

毕竟使用命令也是少数场景
直接获取变量的值才是多数场景
这个美元符号感觉像上世纪的语法 (
建议：
使用py的模板字符串语法 i"pip install {pkg}"
区分
"pip install pkg"

或者只有在命令中变量才需要使$开头

你看看怎么样

[Ansurfen]

i"pip install {pkg}" 如果用这样的语法的话，做代码提示就会很奇怪，而且一般是不会做字符串内的代码提示吧？
我预期的是打pip的时候，会浮现install这个候选词，然后进行代码提示