Re: go Away()


  • Impossible Mission - B

    @blakeyrat said in Re: go Away():

    @masonwheeler I use VS Code every fucking day for TypeScript. It doesn't have anything I'd call an IDE feature.

    :wtf: Wow, seriously?

    That's really messed up.


  • Garbage Person

    @ben_lubar So you’re not answering my question, just repeating your assertion.



  • @dkf said in Re: go Away():

    when they're on the main branch (master, trunk, davetheboss, whatever you want to call it) those warnings should be crushed out if possible as they do indicate a potential problem.

    Argh! In my current project, compiler errors are treated as fatal; the compiler immediately stops, so you can never fix more than one error at a time, but hundreds of warnings are completely ignored. Including warnings like "This violates language rule and can produce unpredictable results; it will probably be an error in a future version of the compiler." :facepalm: And unfortunately, it isn't within my job description to fix them.


  • Impossible Mission - B

    @hardwaregeek What language are you working with?

    I've seen some cases where that happens in Delphi, due to its single-pass structure. But it also happens in a lot of compilers that use multiple passes; if you get errors on one pass it will report all of them and then terminate, and so if you fix those, you then progress to the next pass and get errors from it. (Including some very mature compilers such as CSC.)



  • @ben_lubar said in Re: go Away():

    If you have a function named getValue that returns a string and is documented to be "a function" and your static analysis tool says that functions exported by the library are unused and should be deleted, pretty much every single thing I just said is a bad thing you should fix.

    why?


  • kills Dumbledore

    @masonwheeler said in Re: go Away():

    if you get errors on one pass it will report all of them and then terminate, and so if you fix those, you then progress to the next pass and get errors from it

    99 little errors in the code
    99 little errors
    you take one down and hack it around
    658465487 little errors in the code


  • ♿ (Parody)

    @jaloopa I got 99 errors but an unused variable ain't one.


  • đźš˝ Regular

    @masonwheeler said in Re: go Away():

    @blakeyrat said in Re: go Away():

    @masonwheeler I use VS Code every fucking day for TypeScript. It doesn't have anything I'd call an IDE feature.

    :wtf: Wow, seriously?

    That's really messed up.

    From what little I've seen it's got syntax highlighting, code snippets, code navigation, inline documentation, code formatting, smart autocompletion, compiler integration (including realtime warning and error highlighting), SCM integration, interactive debugging; but refactoring isn't quite there yet.



  • @zecc said in Re: go Away():

    From what little I've seen it's got syntax highlighting, code snippets, code navigation, ... code formatting, ... smart autocompletion,

    Yes, but that's text editor stuff.

    inline documentation,

    That doesn't work for me, if it has it.

    compiler integration (including realtime warning and error highlighting),

    It does have warning and error highlighting, and it has a "build" button, but I couldn't figure out how to get the "build" button to actually build my TypeScript project. Possibly because I'm using Gulp, due to there being several post-build steps to turn the TypeScript into a Chrome extension. (Since I can just type "gulp" once in a CLI, or hit up-arrow enter every subsequent time, I haven't bothered to fix this.)

    SCM integration,

    It might have that, I have to admit I've never tried to set it up.

    interactive debugging;

    Nope, not for Chrome extensions at least. Which doesn't surprise me I suppose, since that's a somewhat rare project type. (Fortunately, Chrome's built-in debugger does ok with them, and reads the "source map" data that shows you the .ts source and not the .js source.)


  • Impossible Mission - B

    @zecc In TypeScript? (Apparently the feature set differs by language, if @blakeyrat is to be believed.) If so, how does that not constitute "anything I'd call an IDE feature" ??? And if not, what language are you working with?


  • Considered Harmful

    @blakeyrat said in Re: go Away():

    It does have warning and error highlighting, and it has a "build" button, but I couldn't figure out how to get the "build" button to actually build my TypeScript project.

    Yeah, the button just whips up a shell and runs a couple of commands. Nothing near an IDE integration.


  • ♿ (Parody)

    @pie_flavor said in Re: go Away():

    @blakeyrat said in Re: go Away():

    It does have warning and error highlighting, and it has a "build" button, but I couldn't figure out how to get the "build" button to actually build my TypeScript project.

    Yeah, the button just whips up a shell and runs a couple of commands. Nothing near an IDE integration environment for development.


  • đźš˝ Regular

    @blakeyrat said in Re: go Away():

    @zecc said in Re: go Away():

    From what little I've seen it's got syntax highlighting, code snippets, code navigation, ... code formatting, ... smart autocompletion,

    Yes, but that's text editor stuff.

    I agree for the most part, but smart autocompletion starts getting into "this editor really understands code rather than just recognize symbols" territory.

    SCM integration,

    It might have that, I have to admit I've never tried to set it up.

    Well, it integrates with git only by default, but it should just magically set itself up if you open a directory under git's purview.

    As for rest, I'm just not experienced enough with VSCode to help you, sorry. Not that you asked anyway.


  • Impossible Mission - B

    @boomzilla said in Re: go Away():

    integration environment for development

    No, I'm pretty sure we don't want any IEDs on our computers.


  • :belt_onion:

    @greybeard said in Re: go Away():

    @sloosecannon said in Re: go Away():

    //This is a library function, it's not used in the project but must be public

    Such things should be referenced from tests.

    That's true, but that puts us in "Test the getter" territory, which is... not ideal.

    That was the example that came to my head though, there are other reasons to ignore (and document) that particular error...



  • @masonwheeler said in Re: go Away():

    @hardwaregeek What language are you working with?

    SystemVerilog

    This particular compiler has a max_errors option, which for some reason is set to 1. So it sees one error and immediately quits. It doesn't even read the next line. I don't think that's the default; one of the many warnings the compiler spews is that max_errors is specified multiple places, and it's using the one passed on the command line by the script that wraps the whole build process. Which, AFAIK, can't be overridden from the script's own command line.


Log in to reply