Proposal Paper

The proposal's paper is the same as the previous paper, and I also like to write this paper. I have been skiing for 14 years, so this is what I am interested in. In the process of writing this document, I heard a contradictory opinion favorably and favorably to the helmet. My father wrote an article about why he should not wear ski helmets, but I felt uncomfortable as he was wearing a ski helmet during skiing. The convincing evidence I found in several places backed up personal preferences, and it helped me prove my position with a fast ski helmet.

Processing, detailed overview of the proposed document, and preliminary bibliography. Proposals are submitted to the evaluation team at regular meetings. This is often referred to as a "tutorial" session and is designed to help students confirm the focus and scope of the article is correct. In appropriate cases, the scoring team will assist in solving problems to be solved, guiding to other sources, or suggesting other methods. The outline should be prepared with thought and attention. The correct framework is outlined as a guide for organizing tools and writing articles. Efforts to get into the outline will bring high return. Time to improve the outline - use it to ensure its integrity and richness, through its process and logic, and to construct research - the relationship with success of the overall effort is usually closely and direct

There are five phases in this proposal, outlined in this document. Each suggestion is the original Scarecrow or Phase 0. At this level, they have not been submitted to the Technical Committee or have not been rejected, but they have not reached the criteria for entering the next stage. Npm init -f && npm i ava@1.0.0 - beta 3 @ babel / preset - env ​​@ 7.0.0 - beta. 42 @ babel / preset - stage - 0 @ 7.0.0 - beta. 42 @ babel / register @ 7.0.0 - beta.42 @ babel / polyfill @ 7.0.0 - beta. 42 @ babel / plugin - transform - runtime @ 7.0.0 - beta. 42 @ babel / runtime @ 7.0.0 - beta. devYou adds the following line to the package.json file:

Implementors should also be interested in the proposal - the proposal without implementor's support is dead. In fact it is advisable to enter this level with support by at least one browser implementation, high fidelity polyfil, or build time converter like Babel.

At that time I chose Babel. Last year, I submitted PR: Pattern Matching on implementation of the new function proposed by TC - 39 Phase 0. The champion responsible for the TC - 39 proposal has changed, so we need to update it now. This is PR, I am continuing to consider specifications. Before the start of GSoC, I sent a tweet to Sean (one of the owner of webpack) asking if Webpack could provide some project on AST analysis (this is what I want to focus on ). Shawn immediately answered and gave me a proposal for depth range analysis. It is to implement a new intuitive and automatic new tree shake function. I think this is cool and it will be an exciting challenge for me.