9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: William Linkmeyer <wlink10@gmail.com>
To: plan9 <9fans@9fans.net>
Subject: [9fans] Better Code Snippets & Suggestions
Date: Mon, 22 Feb 2021 18:07:05 -0500	[thread overview]
Message-ID: <CA6DFE7A-EF62-44F6-9964-DB18E43521F4@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

Dearest Nines,

I’ve been reading these email chains for about three years now. You’ve all taught me quite a bit. I understand that this will be a bit off-topic as it’s not directly related to Plan9. So be it. I wanted to start a chain and chime in on something that I do have experience with.
I’ve been developing a code suggestion platform. The concept is simple relatively simple. As the programmer is typing, patterns in the given code block are identified and compared to a database of tagged code snippets. The code snippet that is most relevant will be presented to the programmer as a suggestion.
The code snippets all come originally from Stack Overflow, GitHub, and my own programs. I’m in the process of tagging these snippets for important features such as purpose, list of operations, any applicable design patterns, paradigms, etc. The more “essential” features are being tagged as well — features such as the number of arguments, return type, etc. 
It’s an interesting project to me. While I think that it’s going well, I’m certain that the large-brain folk here have important commentary on it.

With Peace,
Will
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4f7afadf357a15b1-Mde89233e3e131ea3f441c36d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2121 bytes --]

             reply	other threads:[~2021-02-22 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 23:07 William Linkmeyer [this message]
2021-02-23  1:10 ` Skip Tavakkolian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA6DFE7A-EF62-44F6-9964-DB18E43521F4@gmail.com \
    --to=wlink10@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).