-
Many tests for impala are broken because we currently print types such as `fn(i32) -> i32` as `fn(i32, fn(i32))`. The code that did the pretty printing previously is now commented out in [src/impala/s…
-
### Environment
- OS and version: Windows_NT x64 10.0.19043
- VS Code: Version: 1.90.0 (user setup)
- OS and version of remote machine (if applicable): ARM Linux
- GDB / LLDB version: aarch64-linux-g…
-
```
ASPath objects accepts an ASPathSegment object in its 'segments' field.
However, this field is not printed when representing the object. Only the
'data' field is printed.
When an object is decod…
-
### Motivation: Why do you think this is important?
Improve printing
### Goal: What should the final outcome look like, ideally?
Pretty.
### Describe alternatives you've considered
None
### Pr…
-
```
ASPath objects accepts an ASPathSegment object in its 'segments' field.
However, this field is not printed when representing the object. Only the
'data' field is printed.
When an object is decod…
-
The specific use-case I have in mind is printing stack traces.
For example, here's some Clojure code followed by the JSON it produces.
```clojure
(println
(cheshire.core/generate-string (Throwa…
-
Pretty printing is not pretty enough in my opinion. We should check if a fragment parses and then use the original source.
-
**Describe the bug**
Not exactly sure if this is a bug, but at least a gap. I have moved away from using the Planners and rely on "vanilla" function calling. Yet my tools that I defined can be chaine…
-
Pretty printing of yaml file.
Scanning recursively for yaml files and printing a birds eye view off applied patches in a project could be handy too.
xendk updated
9 years ago
-
Bug type: Debugger
-GDB version: 9.2 (installed using "apt install gdb")
- OS and Version: wsl ubuntu 20.04 running on windows 10
- VS Code Version: 1.62.3
- C/C++ Extension Version: v1.8.0-insi…