<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Kristóf,<div class=""><br class=""></div><div class="">I read your proposal and left some suggested comments in the Google Doc.</div><div class=""><br class=""></div><div class="">The problem you’re tackling is really important and you’ve proposed an exciting avenue to address it!</div><div class=""><br class=""></div><div class="">Because the project is so ambitious and your proposal is a bit light on details, I think you should be very explicit about the success criteria. For static analyzer GSoC proposals, the most important criterion is typically that the feature is turned on by default by the end of the project. You should include a plan with specifics of how and when you will evaluate whether the feature is ready to be turned on for all users of the analyzer. In particular this should include:</div><div class=""><br class=""></div><div class="">* How will you evaluate whether a particular bug report got better or worse with your approach?</div><div class="">* What kinds of codebases will you support and evaluate it on? C? C++? Objective-C?</div><div class="">* How will you determine what the performance cost (running time, memory) is?</div><div class="">* Specifically, how will you know when the feature is ready to be turned on by default?</div><div class=""><br class=""></div><div class="">If you don’t think that enabling the feature by default by the end of GSoC will be achievable, then you should consider reducing the scope of the project. Is there a subset of the proposal that is achievable to turn on by default by the of GSoC?</div><div class=""><br class=""></div><div class="">Devin</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Apr 6, 2019, at 12:05 PM, Kristóf Umann <<a href="mailto:dkszelethus@gmail.com" class="">dkszelethus@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class="">Hi!<div class=""><br class=""></div><div class="">Thank you so much for all the feedback I was given on my problem statement! My formal proposal isn't finished just yet (still need to add references, make the formatting nicer, add proper contact info, maybe some more details on my proposed solution), but here is the link to it:<br class=""><br class=""><a href="https://docs.google.com/document/d/1ci1BCAKojPlqIxIw1J_K2dnATA3z01PuwR_vHJS55TI/edit?usp=sharing" class="">https://docs.google.com/document/d/1ci1BCAKojPlqIxIw1J_K2dnATA3z01PuwR_vHJS55TI/edit?usp=sharing</a></div><div class=""><br class=""></div><div class="">Any and all feedback is welcome!</div><div class=""><br class=""></div><div class="">Link to my previous letters regarding GSoC:<br class=""><a href="http://lists.llvm.org/pipermail/cfe-dev/2019-April/061900.html" class="">http://lists.llvm.org/pipermail/cfe-dev/2019-April/061900.html</a><br class=""></div><div class=""><a href="http://lists.llvm.org/pipermail/cfe-dev/2019-March/061500.html" class="">http://lists.llvm.org/pipermail/cfe-dev/2019-March/061500.html</a><br class=""></div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Kristóf</div></div></div></div></div></div></div></div></div></div></div></div>
</div></blockquote></div><br class=""></div></body></html>