Meeting Feedback Week 2

How well its written Transform, correcting ,suggestions

• Automatic / manual checking
• User decides what to do
• Suggested

Analysis - feedback Automatic transfomation - highlight to the user what to do Semi manual transformation - user starts refactoring process

• LOOk at procedural language More focus on functional

DO better than exisitng tools

AIM : more high level

Fhsarp intellisense

• Error messeages intellisense as good as possible - make them better

Error further downs program, not where you are at

Take into acoount names of identifies, how code is laid out

WRite it better - differ

• more informaiton

• layout

• names - LST - list - interpret what programmer from name, e.g. identifies

  • longer, local variable longer, or not

• Look for things similar to name

Indentation errors

Better set of tools - miss out bracket instead of tabs Look for brackets Evaluating myself

Todo

• Classify types of thing into seperate things, difficulty
• Investigate context, which things have been done before, think about the different way to get heurisitc
• Categories ( outside F #)
• Find ideas from researching project

Deliverable

• 2 types - unfinished, finished
• Code that doesnt parse
• Improvement

Misleading errors - probabbly

Suggests as to how to improve, make it correct

Artifical intelligen , ML for names

Interim

• Doable
• evaluate

Talking about changing a program into make it better

• Name transformation
• Functional abstraction - take a bit of syntax tree, write it as a function
  • 2 ways, give it name or anon, let programmer decide

Literature survey

• Research the different ways to make heurisitcs