每天推薦一個 GitHub 優質開源項目和一篇精選英文科技或編程文章原文，歡迎關注開源日報。交流QQ群：202790710；電報群 https://t.me/OpeningSourceOrg
今日推薦開源項目：《Majestic》GitHub地址：https://github.com/Raathigesh/majestic
推薦理由：Majestic是一個電子應用程序，提供了一個用Jest運行測試的UI。Jest CLI本身提供了當今最好的測試體驗之一,但Majestic試圖通過提供一個豐富的用戶界面來在開發/測試循環期間擴展它。
特徵：
• 通過點擊運行整個項目，文件或特定的測試
• 觀看整個項目，文件或測試
• 點擊更新特定的快照「
• 內聯覆蓋報告
• 支持打字稿項目
• 支持Create-React-App開箱即用
• 快速搜索，搜索您的所有測試（It）聲明
• 失敗摘要在單個屏幕中顯示所有測試失敗。跨多個文件出現故障時很有用。
• 點擊一個按鈕，在您的編輯器中找到一個特定的測試
如果你有一個外部的jest配置文件，你應該有一個指向文件的jestConfig鍵，package.json如下所示：
{
「 name 」：「 my-awesome-proj 」，
「 version 」：「 0.1.0 」，
「 description 」：「 .. 」，
「 jestConfig 」：「 ./jest-custom.config.js 」
}
今日推薦英文原文：《Using Deep Learning to Understand Your Source Code》作者：Jesus Rodriguez
原文鏈接：https://medium.com/@jrodthoughts/using-deep-learning-to-understand-your-source-code-28e5c284bfda
推薦理由：使用機器學習來理解你的源代碼？正是沒錯。你知道你的程序出錯，但是不知道哪裡出錯？想找個人幫幫忙？嘿嘿！
Using Deep Learning to Understand Your Source Code
This should be a familiar experience to any programmer. You are immersed writing code in a static language like C# or Java, you have happily written a few hundred lines of this beautiful algorithm and then you press compile hoping to see the results of your great work. To your frustration, the compiler outputs an error message in bold red lines indicating that you missed a semicolon in line 17. At that point, you can』t avoid thinking why the stupid compiler doesn』t just add the semicolon to the end of line 17 and move on instead of telling you. Seriously, how hard could that be? Well, it turns out its pretty hard. The reason for the compiler』s frustrating behavior is that code interpreters and compilers today and extremely efficient analyzing the syntactic aspects of a problem but very limited when comes to understand the semantics of the program or our intentions as a programmer.
Many bugs in a program are not solely derived from the syntax of the program due to the higher level semantic aspects. Consider the following code snippet that should indicate an agent to turn right. While it is very obvious to a programmer that the code is wrong as it us using the left angle to turn right, mainstream compilers are completely incapable to detect that flaw.
When a programmer looks at a specific source code, it seems more than instructions and functions and it starts forming an understanding of the goals and functionality of the program. Wouldn』t it be great if compilers were able to formulate a similar level of understanding? The irony is that recent advancements in deep learning areas such as natural language understanding(NLU) allow artificial intelligence(AI) agents to understand highly complex communication structures such as human conversations while we still can』t figure out highly structured texts such as computer programs.
Recently, Microsoft Research published a paper that proposes a technique that combines NLU techniques with mathematical logic to detect semantically-related bugs in source code. The key idea of the technique is to form a semantic representation of source code that complements its syntactic structure in order to detect more abstract errors.
Titled 「Learning to Represent Programs with Graphs」, the Microsoft Research paper introduces a deep learning method that transform a specific source code into a graph structure. The nodes of the graph include the tokens of the program (that is, variables, operators, method names, and so on) and the nodes of its abstract syntax tree (elements from the grammar defining the language syntax such as If Statement). The program graph contains two different types of edges: syntactic edges, representing only how the code should be parsed, such as while loops and if blocks; and semantic edges that are the result of simple program analyses.
Having semantic edges allows the deep learning model to represent all sorts of high level knowledge constructs that resemble the way programmers analyze a specific source code. For instance, semantic edges such as 「LastUse」 connect a variable to the last time it may have been used in program execution (which in the case of loops can be later in the source code), 「LastWrite」 edges connect a variable to the last time it was written to, or as 「ComputedFrom」 edges connect a variable to the values it was computed from. From that perspective, a large group of semantic edges can help to simulate the human interpretation process of a computer program.
In order to validate their technique, the Microsoft researchers focused on two specific types of semantic errors. The VARMISUSE task is focused on detecting variable misuses in code is a task that requires understanding and reasoning about program semantics. To successfully tackle the task one needs to infer the role and function of the program elements and understand how they relate. For example, given the following program, the task is to automatically detect that the marked use of clazz is a mistake and that first should be used instead.
var clazz=classTypes["Root"].Single() as JsonCodeGenerator.ClassType; Assert.NotNull(clazz); var first=classTypes["RecClass"].Single() as JsonCodeGenerator.ClassType; Assert.NotNull( clazz ); Assert.Equal("string", first.Properties["Name"].Name); Assert.False(clazz.Properties["Name"].IsArray);
Similarly, the VARNAMING task corrects infers the correct variable name based on a specific syntaxtic representation of a source code. For instance, the following example from the C# Roslyn compiler detected incorrect uses of the parameter filepath and the field _filePath, which are easily mistaken for each other.
The use of Program Graphs are not only an interesting theoretical exercise but it proven to be more efficient than many alternatives in the deep learning space. The Microsoft team conducted experiments analyzing over 2.9 million lines of source code and the new technique yielded substantially better results that more traditional methods such as bidirectional recurrent neural networks. Although the methods are highly experimental, program graphs seem to be a step towards making compilers are intelligent as human programmers.
每天推薦一個 GitHub 優質開源項目和一篇精選英文科技或編程文章原文，歡迎關注開源日報。交流QQ群：202790710；電報群 https://t.me/OpeningSourceOrg
