How to install it on Linux?

will it work in visual studio express 2013 ?

Added a 64-bit Linux build.

It seems that Caide does not work with C++11 feature =delete. Caide removes unused declaration of constructor but remains attributes of this declaration.

For example, in solution file we have

class Test {
public:
	Test(int n) : n(n) {}
private:
	Test() = delete;
	int n;
};

void solve(istream& in, ostream& out) {
	Test a(1000);
}

Caide converts it to submission.cpp:

class Test {
public:
	Test(int n) : n(n) {}
private:
	 = delete;
	int n;
};

void solve(istream& in, ostream& out) {
	Test a(1000);
}

Compiler fails on file submission.cpp with error error C2059: syntax error : '='.

Is it possible to fix it?

Another bug is removing method that is called from destructor (in case if destructor is not called explicitly).

Because the code is rather huge, I put it on Pastebin: http://pastebin.com/CRQDgguM. The first two cases are failed, the last one worked fine, but it is not convenient to write in such way during coding.

To continue reporting streak just want to mention strange thing (not a bug actually).

I bet lots of participants have some defines like

#ifdef _WIN32
#define LLD "%I64d"
#else
#define LLD "%lld"
#endif

to make their code work under different environment.

Caide inliner module removes this ifdef and you need to fix you submission.cpp file manually. It is not very convenient to repeat this process every time. Is there any opportunity to tell inliner not to remove this ifdef?

can i get (caide) for VS 2015 ??!

Caide 2.1 changes:

• Visual Studio 2015 support
• CodeChef and Codeforces fix
• Several improvements in C++ inliner
• Better cross-distro compatibility for Linux builds

How to use it for windows ?

First of all, thank you very much for this awesome tool.

Second, after the most recent update to VS2015 the following needs to be added to clang_options in caide.ini: -D__EDG__,

I published 2.2 release. This release contains improvements in C++ inliner. In particular, unused namespaces and comments attached to unused declarations are now removed. Make sure to have -fparse-all-comments clang option in your caide.ini file.

Note: If you use latest release of VS 2015, you need to add the clang option -D__EDG__ in your caide.ini file. Thanks to Jacob for catching this.

Also, in light of recent cin/scanf fiasco, I'd like to remind that you can configure caide to use printf/scanf, fast I/O or any other kind of I/O. All you have to do is modify the signature of solve function and make corresponding changes in 3 template files: main_template.cpp, solution_template.cpp and test_template.cpp (the last one is quite large but you're interested only in runTest function). A sample implementation for printf/scanf is here: https://github.com/slycelote/caide/tree/release/libcaide/doc/samples/cstyle-io

Another VS update broke the extension again... A hack to fix this is to add -D__is_assignable=__is_nothrow_assignable to clang_options config entry.

caide version 2.3 is out with support for Visual Studio 2017 and fixes in HackerRank and CodeChef parsers.

Hi. I was looking for a C++ code inliner, and found this one. I built it for Mac and looks like it's working, but I have some questions.

First, I parsed some problem and manually entered the correct sample output. But after I compile and run it, it outputs

Running test case1
...correct output goes here...

Results summary
_______________
Outcome	Count
Error	1

case1: Testwasnotrun

Why error and Testwasnotrun?

The more general question is how to use it in conjunction with some IDE? It would be convenient to use CMake to create a project with one target for every problem. Is there a way to configure problemID to be just one letter, not including any contest details? And what's the expected workflow for problems that cannot be parsed?

Thanks for the amazing tool!
I am not able to parse tasks through CHelper in Chrome. I read many forums but all in vain. It would be great if u could explain how I can do parsing.
Thanks :)

In the Visual Studio 2017 Community Edition i have installed VsCaide extension..... But When I build a solution it is showing build errors...... 499 errors its showing...... cmath, cerno etc....... Can you fix it ?

how to solve this problem https://imgur.com/a/ur5ej ?

is any one here using this tool with visual studio 2017 and work with it properly, i need his help in guiding me !!

YouTube Tutorial on how to use VsCaide: https://youtu.be/qNKBdqifxpU

New in version 2.4:

• Support Competitive Companion browser extension for problem parsing.
• Better test editing GUI in VsCaide, see new screenshot (thanks to @Predelnik)
• Autodetect latest Windows SDK in vcxproj template, removing the need to install Universal SDK (thanks to @aybassiouny)
• Update bundled MinGW headers: in particular, fixes missing std::to_string.
• -std=c++14 is now default, -std=c++1z is available for C++17 support
• Bug fixes in C++ inliner
• Improve automated detection of compilation flags when system headers are used.

Download from github here. Visual Studio extension will be published to the marketplace soon.

Can you port it over to Sublime Text 3 because many competitive programmers use a lightweight ide like sublime text instead of Visual Studio

Fixed in version 2.4.1:

• An issue with initialization when a c++ compiler cannot be found.
• Visual Studio 2019 compatibility for the extension

Awesome job, I wish I had known about this tool earlier.

I've noticed a bug where the inliner removes code which is only used inside static_assert's:

using int2 = int;                             // this line is removed in submission.cpp
static_assert(is_same<int2, int>::value, ""); // this line is kept, resulting in a compile error

I am trying to use caide with CHelper browser extension. It seems that for GCJ website this coupling doesn't work. On VS General Output window I can see the following message every attempt to parse a problem:

'gcj3' not supported

Version 2.5.0 is released on Github. I'll upload VS extension to the marketplace in a few days.

General

• Default Competitive Companion port changed to 10043.
• Fixes in CodeForces and CodeChef parsers
• Fix incorrect parameter passthrough in default Topcoder test template

C++ inliner:

• Update all builtin headers to latest versions (libstdc++ 10.1.0, MinGW 7.0, Clang 10.0). Allows using latest language and STL features.
• Default language setting changed to C++17 (-std=c++17).

Visual Studio extension:

• Drop compatibility with VS 2013 and VS 2015
• Remove deprecation warning in VS 2019
• Fix a regression when build output would go into the root directory of the disk
• Double-clicking a caide solution will now properly activate Caide window.
• Slightly better look in dark mode.

New in version 2.6.0:

• Drop support for 32-bit Windows
• Support 'regex' problem type for Competitive Companion
• Fix CodeChef contest parser
• Automatic check for updates in the command line application (can be disabled via config)

VS extension will be published shortly.

New in version 2.7.0:

• Allow overriding problem ID when parsing
• Display runtime per test
• Add verbose_test_report option to display results of all tests rather than just failed ones
• Fix hanging HTTP server on Windows

Does it support Kotlin? İf can you please add it

New in version 2.8:

• Add warning when a template was updated both upstream and by the user
• Display input file in main template for regex type
• Autogenerate class constructor in C++ TopCoder template
• Visual Studio extension:
  • Avoid VS crashes
  • Use colors (mostly) consistent with selected theme.

Any idea why: LINK : fatal error LNK1104: cannot open file 'C:\Home\Caide2021\cpplib\Debug\cpplib.lib'

Added support for VS 2022.

New in 2.10:

• LeetCode support.
• C++ inliner:
  • Preserve Topcoder class constructor and solution method automatically.
  • Pull all include directives to the beginning of inlined file.
• VS extension:
  • (Regression fix) Automatically archive problem when VS project is deleted.
  • Avoid errors when trying to delete directories locked by another program (e.g. file explorer) or VS itself.
  • Minor UI improvements.

Can I use it on mac m1 pro chip ?