@Lexicos Hope => operator can return unset too when f(){} function define could support return unset.
It's merely a small hope. As you have said, you may add support for functions to return unset by default instead of a "" when what to return is not specified. Also, the v2 plugin for VSCode can aready examine it. So, I hope the same would apply to => too at that time.
For example, ()=>unset, a function just to make codes run in some situations if it has no specific alternative temporarily.
Hope => operator can support return unset Topic is solved
Re: Hope => operator can support return unset Topic is solved
=> expr creates a function body literally equivalent to return expr, as ListLines shows. There is no reason for => unset to be unsupported if return unset is supported.
Re: Hope => operator can support return unset
@Lexicos That's hears great. It would be better if true?Unset:1 could also be supported at the same time, only when true?Unset:1 is behind return/=>, just like what happened to Unset.
Return to “AutoHotkey Development”
Who is online
Users browsing this forum: No registered users and 3 guests