search for: jvapen

...39;ll be running a BoF on this at the October dev meeting? J >> >> --paulr >> >> >> >> *From:* llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] *On Behalf Of *Reid >> Kleckner via llvm-dev >> *Sent:* Wednesday, June 20, 2018 6:12 PM >> *To:* JVApen at gmail.com >> *Cc:* llvm-dev >> *Subject:* Re: [llvm-dev] Bug-closing protocol >> >> >> >> Thanks for taking the time to report bugs! I think you are responsible >> for filing the most high-quality clang-cl bugs. >> >> >> >> I hope...

So Reid, you'll be running a BoF on this at the October dev meeting? ☺ --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Reid Kleckner via llvm-dev Sent: Wednesday, June 20, 2018 6:12 PM To: JVApen at gmail.com Cc: llvm-dev Subject: Re: [llvm-dev] Bug-closing protocol Thanks for taking the time to report bugs! I think you are responsible for filing the most high-quality clang-cl bugs. I hope our bug responses continue to be helpful and informative, but things do often get lost in translatio...

...now, the code is ifdef-ed out for clang as it won't link anyhow. In conclusion: I really respect the work you do, this puts the standard on a high level. Taking the time to inform the bug logger is a must have. However, it is not the only place were we as bug loggers are lacking information. JVApen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180619/0ad422fa/attachment-0001.html>