River Riddle

Thanks for the report, we'll take a look!

Should have a fix for this out by the next release!

Thanks for reporting! @walter-erquinigo This looks like a bug in LLDB, it crashes before we even get to our REPL code AFAICT, wonder if it just isn't prepared to handle...

Thanks for the report! For the longest time this has been the intentional behavior -> we don't resolve things that don't get referenced. As we've been bringing up module initializers/top-level...

Thanks for reporting this! We've identified an issue with the currently shipped SDK where we're accidentally stripping symbols used by the debugger for JIT debugging. We're working on a fix,...

The problem is of a much larger scope than this issue, almost none(only 3) of the operations in the LLVM dialect have verification.

Thanks for filing this issue! This might be related to an issue with computing document symbols for traits (that we've got a fix cooking for). Does this happen when you...

@ftynse yes, we can't use the standard LLVM type parser to support named structs. It relies on the fact that the struct types have already been printed/parsed and elides the...

Why would we even need to worry about loops that would never execute? Shouldn't these just be DCE'd?

Yep, thanks. I was thinking of something completely different. On Thu, Oct 17, 2019 at 8:47 PM Uday Bondhugula wrote: > Why would we even need to worry about loops...