[df] Avoid calling JIT again in RDataFrame destructor

This was done to workaround #15399,
but now that the controlled leaks have been removed it is not necessary anymore.

Author: vepadulano

tree/dataframe/inc/ROOT/RDataFrame.hxx

@@ -55,14 +55,6 @@ public:
    RDataFrame(ULong64_t numEntries);
    RDataFrame(std::unique_ptr<ROOT::RDF::RDataSource>, const ColumnNames_t &defaultColumns = {});
    RDataFrame(ROOT::RDF::Experimental::RDatasetSpec spec);
-
-   // Rule of five
-
-   RDataFrame(const RDataFrame &) = default;
-   RDataFrame &operator=(const RDataFrame &) = default;
-   RDataFrame(RDataFrame &&) = default;
-   RDataFrame &operator=(RDataFrame &&) = default;
-   ~RDataFrame();
 };
 
 namespace RDF {

tree/dataframe/src/RDataFrame.cxx

@@ -2226,17 +2226,6 @@ RDataFrame::RDataFrame(ROOT::RDF::Experimental::RDatasetSpec spec)
 {
 }
 
-RDataFrame::~RDataFrame()
-{
-   // If any node of the computation graph associated with this RDataFrame
-   // declared code to jit, we need to make sure the compilation actually
-   // happens. For example, a jitted Define could have been booked but
-   // if the computation graph is not actually run then the code of the
-   // Define node is not jitted. This in turn would cause memory leaks.
-   // See https://github.com/root-project/root/issues/15399
-   fLoopManager->Jit();
-}
-
 namespace RDF {
 namespace Experimental {