3 ms·
I once tried to link error messages directly to the offending line in their open source code, such that it would be clear to everyone what is broken. It never w
by 1970-01-01 3y ago
I once tried to link error messages directly to the offending line in their open source code, such that it would be clear to everyone what is broken. It never worked correctly, and I stopped trying. If anyone can create an elegant way to do that, it would be a game changer for open source.
- jasomill 3y agoLike a stack trace? jtm@socrates ~ $ dotnet new -o foo console >/dev/null 2>&1 && cd foo && cat > Program.cs && dotnet build >/dev/null 2>&1 && dotnet run String? bar = null; bar.GetHashCode(); ^D Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object. at Program.<Main>$(String[] args) in /Users/jtm/foo/Program.cs:line 2 While not novel, I agree that always including stack traces with error messages, hidden behind a disclosure widget or in a log file to avoid overwhelming non-programmers, is extremely helpful in troubleshooting when source is available.
- 1970-01-01 3y agoI tried linking errors to their offending line in GitHub repos, including a diff of local and newest version. Perhaps with some good AI, it could work and be a novel way of fixing open source errors.