├── .github └── workflows │ ├── check-build.yml │ ├── check-pr.yml │ └── deploy.yml ├── .gitignore ├── CMakeLists.txt ├── Makefile ├── README ├── bin ├── build_lists.bat ├── build_lists.sh ├── build_lists_only.bat ├── build_lists_only.sh ├── build_pgms.bat ├── build_pgms.sh ├── build_section_data.bat ├── build_section_data.sh ├── check-html-diffs.sh ├── issues_to_be_moved.sh ├── lint.sh ├── make_dates.py ├── make_paper_titles.py ├── priority_poll.sh ├── sweep_voting_to_wp.sh └── update_status.sh ├── how-to-docs.html ├── meta-data ├── filesystem-section.data ├── fund-index.bat ├── fund-index.sed ├── h-style-index.bat ├── h-style-index.sed ├── lfts-old-section.data ├── lfts-v3-section.data ├── lwg-toc.old.html ├── networking-section.data ├── paper_titles.txt ├── section.data └── tr1_section.data ├── src ├── date.cpp ├── date.h ├── html_utils.h ├── issues.cpp ├── issues.h ├── list_issues.cpp ├── lists.cpp ├── mailing_info.cpp ├── mailing_info.h ├── metadata.cpp ├── metadata.h ├── report_generator.cpp ├── report_generator.h ├── section_data.cpp ├── sections.cpp ├── sections.h ├── set_status.cpp ├── status.cpp ├── status.h └── toc_diff.cpp └── xml ├── issue0001.xml ├── issue0002.xml ├── issue0003.xml ├── issue0004.xml ├── issue0005.xml ├── issue0006.xml ├── issue0007.xml ├── issue0008.xml ├── issue0009.xml ├── issue0010.xml ├── issue0011.xml ├── issue0012.xml ├── issue0013.xml ├── issue0014.xml ├── issue0015.xml ├── issue0016.xml ├── issue0017.xml ├── issue0018.xml ├── issue0019.xml ├── issue0020.xml ├── issue0021.xml ├── issue0022.xml ├── issue0023.xml ├── issue0024.xml ├── issue0025.xml ├── issue0026.xml ├── issue0027.xml ├── issue0028.xml ├── issue0029.xml ├── issue0030.xml ├── issue0031.xml ├── issue0032.xml ├── issue0033.xml ├── issue0034.xml ├── issue0035.xml ├── issue0036.xml ├── issue0037.xml ├── issue0038.xml ├── issue0039.xml ├── issue0040.xml ├── issue0041.xml ├── issue0042.xml ├── issue0043.xml ├── issue0044.xml ├── issue0045.xml ├── issue0046.xml ├── issue0047.xml ├── issue0048.xml ├── issue0049.xml ├── issue0050.xml ├── issue0051.xml ├── issue0052.xml ├── issue0053.xml ├── issue0054.xml ├── issue0055.xml ├── issue0056.xml ├── issue0057.xml ├── issue0058.xml ├── issue0059.xml ├── issue0060.xml ├── issue0061.xml ├── issue0062.xml ├── issue0063.xml ├── issue0064.xml ├── issue0065.xml ├── issue0066.xml ├── issue0067.xml ├── issue0068.xml ├── issue0069.xml ├── issue0070.xml ├── issue0071.xml ├── issue0072.xml ├── issue0073.xml ├── issue0074.xml ├── issue0075.xml ├── issue0076.xml ├── issue0077.xml ├── issue0078.xml ├── issue0079.xml ├── issue0080.xml ├── issue0081.xml ├── issue0082.xml ├── issue0083.xml ├── issue0084.xml ├── issue0085.xml ├── issue0086.xml ├── issue0087.xml ├── issue0088.xml ├── issue0089.xml ├── issue0090.xml ├── issue0091.xml ├── issue0092.xml ├── issue0093.xml ├── issue0094.xml ├── issue0095.xml ├── issue0096.xml ├── issue0097.xml ├── issue0098.xml ├── issue0099.xml ├── issue0100.xml ├── issue0101.xml ├── issue0102.xml ├── issue0103.xml ├── issue0104.xml ├── issue0105.xml ├── issue0106.xml ├── issue0107.xml ├── issue0108.xml ├── issue0109.xml ├── issue0110.xml ├── issue0111.xml ├── issue0112.xml ├── issue0113.xml ├── issue0114.xml ├── issue0115.xml ├── issue0116.xml ├── issue0117.xml ├── issue0118.xml ├── issue0119.xml ├── issue0120.xml ├── issue0121.xml ├── issue0122.xml ├── issue0123.xml ├── issue0124.xml ├── issue0125.xml ├── issue0126.xml ├── issue0127.xml ├── issue0128.xml ├── issue0129.xml ├── issue0130.xml ├── issue0131.xml ├── issue0132.xml ├── issue0133.xml ├── issue0134.xml ├── issue0135.xml ├── issue0136.xml ├── issue0137.xml ├── issue0138.xml ├── issue0139.xml ├── issue0140.xml ├── issue0141.xml ├── issue0142.xml ├── issue0143.xml ├── issue0144.xml ├── issue0145.xml ├── issue0146.xml ├── issue0147.xml ├── issue0148.xml ├── issue0149.xml ├── issue0150.xml ├── issue0151.xml ├── issue0152.xml ├── issue0153.xml ├── issue0154.xml ├── issue0155.xml ├── issue0156.xml ├── issue0157.xml ├── issue0158.xml ├── issue0159.xml ├── issue0160.xml ├── issue0161.xml ├── issue0162.xml ├── issue0163.xml ├── issue0164.xml ├── issue0165.xml ├── issue0166.xml ├── issue0167.xml ├── issue0168.xml ├── issue0169.xml ├── issue0170.xml ├── issue0171.xml ├── issue0172.xml ├── issue0173.xml ├── issue0174.xml ├── issue0175.xml ├── issue0176.xml ├── issue0177.xml ├── issue0178.xml ├── issue0179.xml ├── issue0180.xml ├── issue0181.xml ├── issue0182.xml ├── issue0183.xml ├── issue0184.xml ├── issue0185.xml ├── issue0186.xml ├── issue0187.xml ├── issue0188.xml ├── issue0189.xml ├── issue0190.xml ├── issue0191.xml ├── issue0192.xml ├── issue0193.xml ├── issue0194.xml ├── issue0195.xml ├── issue0196.xml ├── issue0197.xml ├── issue0198.xml ├── issue0199.xml ├── issue0200.xml ├── issue0201.xml ├── issue0202.xml ├── issue0203.xml ├── issue0204.xml ├── issue0205.xml ├── issue0206.xml ├── issue0207.xml ├── issue0208.xml ├── issue0209.xml ├── issue0210.xml ├── issue0211.xml ├── issue0212.xml ├── issue0213.xml ├── issue0214.xml ├── issue0215.xml ├── issue0216.xml ├── issue0217.xml ├── issue0218.xml ├── issue0219.xml ├── issue0220.xml ├── issue0221.xml ├── issue0222.xml ├── issue0223.xml ├── issue0224.xml ├── issue0225.xml ├── issue0226.xml ├── issue0227.xml ├── issue0228.xml ├── issue0229.xml ├── issue0230.xml ├── issue0231.xml ├── issue0232.xml ├── issue0233.xml ├── issue0234.xml ├── issue0235.xml ├── issue0236.xml ├── issue0237.xml ├── issue0238.xml ├── issue0239.xml ├── issue0240.xml ├── issue0241.xml ├── issue0242.xml ├── issue0243.xml ├── issue0244.xml ├── issue0245.xml ├── issue0246.xml ├── issue0247.xml ├── issue0248.xml ├── issue0249.xml ├── issue0250.xml ├── issue0251.xml ├── issue0252.xml ├── issue0253.xml ├── issue0254.xml ├── issue0255.xml ├── issue0256.xml ├── issue0257.xml ├── issue0258.xml ├── issue0259.xml ├── issue0260.xml ├── issue0261.xml ├── issue0262.xml ├── issue0263.xml ├── issue0264.xml ├── issue0265.xml ├── issue0266.xml ├── issue0267.xml ├── issue0268.xml ├── issue0269.xml ├── issue0270.xml ├── issue0271.xml ├── issue0272.xml ├── issue0273.xml ├── issue0274.xml ├── issue0275.xml ├── issue0276.xml ├── issue0277.xml ├── issue0278.xml ├── issue0279.xml ├── issue0280.xml ├── issue0281.xml ├── issue0282.xml ├── issue0283.xml ├── issue0284.xml ├── issue0285.xml ├── issue0286.xml ├── issue0287.xml ├── issue0288.xml ├── issue0289.xml ├── issue0290.xml ├── issue0291.xml ├── issue0292.xml ├── issue0293.xml ├── issue0294.xml ├── issue0295.xml ├── issue0296.xml ├── issue0297.xml ├── issue0298.xml ├── issue0299.xml ├── issue0300.xml ├── issue0301.xml ├── issue0302.xml ├── issue0303.xml ├── issue0304.xml ├── issue0305.xml ├── issue0306.xml ├── issue0307.xml ├── issue0308.xml ├── issue0309.xml ├── issue0310.xml ├── issue0311.xml ├── issue0312.xml ├── issue0313.xml ├── issue0314.xml ├── issue0315.xml ├── issue0316.xml ├── issue0317.xml ├── issue0318.xml ├── issue0319.xml ├── issue0320.xml ├── issue0321.xml ├── issue0322.xml ├── issue0323.xml ├── issue0324.xml ├── issue0325.xml ├── issue0326.xml ├── issue0327.xml ├── issue0328.xml ├── issue0329.xml ├── issue0330.xml ├── issue0331.xml ├── issue0332.xml ├── issue0333.xml ├── issue0334.xml ├── issue0335.xml ├── issue0336.xml ├── issue0337.xml ├── issue0338.xml ├── issue0339.xml ├── issue0340.xml ├── issue0341.xml ├── issue0342.xml ├── issue0343.xml ├── issue0344.xml ├── issue0345.xml ├── issue0346.xml ├── issue0347.xml ├── issue0348.xml ├── issue0349.xml ├── issue0350.xml ├── issue0351.xml ├── issue0352.xml ├── issue0353.xml ├── issue0354.xml ├── issue0355.xml ├── issue0356.xml ├── issue0357.xml ├── issue0358.xml ├── issue0359.xml ├── issue0360.xml ├── issue0361.xml ├── issue0362.xml ├── issue0363.xml ├── issue0364.xml ├── issue0365.xml ├── issue0366.xml ├── issue0367.xml ├── issue0368.xml ├── issue0369.xml ├── issue0370.xml ├── issue0371.xml ├── issue0372.xml ├── issue0373.xml ├── issue0374.xml ├── issue0375.xml ├── issue0376.xml ├── issue0377.xml ├── issue0378.xml ├── issue0379.xml ├── issue0380.xml ├── issue0381.xml ├── issue0382.xml ├── issue0383.xml ├── issue0384.xml ├── issue0385.xml ├── issue0386.xml ├── issue0387.xml ├── issue0388.xml ├── issue0389.xml ├── issue0390.xml ├── issue0391.xml ├── issue0392.xml ├── issue0393.xml ├── issue0394.xml ├── issue0395.xml ├── issue0396.xml ├── issue0397.xml ├── issue0398.xml ├── issue0399.xml ├── issue0400.xml ├── issue0401.xml ├── issue0402.xml ├── issue0403.xml ├── issue0404.xml ├── issue0405.xml ├── issue0406.xml ├── issue0407.xml ├── issue0408.xml ├── issue0409.xml ├── issue0410.xml ├── issue0411.xml ├── issue0412.xml ├── issue0413.xml ├── issue0414.xml ├── issue0415.xml ├── issue0416.xml ├── issue0417.xml ├── issue0418.xml ├── issue0419.xml ├── issue0420.xml ├── issue0421.xml ├── issue0422.xml ├── issue0423.xml ├── issue0424.xml ├── issue0425.xml ├── issue0426.xml ├── issue0427.xml ├── issue0428.xml ├── issue0429.xml ├── issue0430.xml ├── issue0431.xml ├── issue0432.xml ├── issue0433.xml ├── issue0434.xml ├── issue0435.xml ├── issue0436.xml ├── issue0437.xml ├── issue0438.xml ├── issue0439.xml ├── issue0440.xml ├── issue0441.xml ├── issue0442.xml ├── issue0443.xml ├── issue0444.xml ├── issue0445.xml ├── issue0446.xml ├── issue0447.xml ├── issue0448.xml ├── issue0449.xml ├── issue0450.xml ├── issue0451.xml ├── issue0452.xml ├── issue0453.xml ├── issue0454.xml ├── issue0455.xml ├── issue0456.xml ├── issue0457.xml ├── issue0458.xml ├── issue0459.xml ├── issue0460.xml ├── issue0461.xml ├── issue0462.xml ├── issue0463.xml ├── issue0464.xml ├── issue0465.xml ├── issue0466.xml ├── issue0467.xml ├── issue0468.xml ├── issue0469.xml ├── issue0470.xml ├── issue0471.xml ├── issue0472.xml ├── issue0473.xml ├── issue0474.xml ├── issue0475.xml ├── issue0476.xml ├── issue0477.xml ├── issue0478.xml ├── issue0479.xml ├── issue0480.xml ├── issue0481.xml ├── issue0482.xml ├── issue0483.xml ├── issue0484.xml ├── issue0485.xml ├── issue0486.xml ├── issue0487.xml ├── issue0488.xml ├── issue0489.xml ├── issue0490.xml ├── issue0491.xml ├── issue0492.xml ├── issue0493.xml ├── issue0494.xml ├── issue0495.xml ├── issue0496.xml ├── issue0497.xml ├── issue0498.xml ├── issue0499.xml ├── issue0500.xml ├── issue0501.xml ├── issue0502.xml ├── issue0503.xml ├── issue0504.xml ├── issue0505.xml ├── issue0506.xml ├── issue0507.xml ├── issue0508.xml ├── issue0509.xml ├── issue0510.xml ├── issue0511.xml ├── issue0512.xml ├── issue0513.xml ├── issue0514.xml ├── issue0515.xml ├── issue0516.xml ├── issue0517.xml ├── issue0518.xml ├── issue0519.xml ├── issue0520.xml ├── issue0521.xml ├── issue0522.xml ├── issue0523.xml ├── issue0524.xml ├── issue0525.xml ├── issue0526.xml ├── issue0527.xml ├── issue0528.xml ├── issue0529.xml ├── issue0530.xml ├── issue0531.xml ├── issue0532.xml ├── issue0533.xml ├── issue0534.xml ├── issue0535.xml ├── issue0536.xml ├── issue0537.xml ├── issue0538.xml ├── issue0539.xml ├── issue0540.xml ├── issue0541.xml ├── issue0542.xml ├── issue0543.xml ├── issue0544.xml ├── issue0545.xml ├── issue0546.xml ├── issue0547.xml ├── issue0548.xml ├── issue0549.xml ├── issue0550.xml ├── issue0551.xml ├── issue0552.xml ├── issue0553.xml ├── issue0554.xml ├── issue0555.xml ├── issue0556.xml ├── issue0557.xml ├── issue0558.xml ├── issue0559.xml ├── issue0560.xml ├── issue0561.xml ├── issue0562.xml ├── issue0563.xml ├── issue0564.xml ├── issue0565.xml ├── issue0566.xml ├── issue0567.xml ├── issue0568.xml ├── issue0569.xml ├── issue0570.xml ├── issue0571.xml ├── issue0572.xml ├── issue0573.xml ├── issue0574.xml ├── issue0575.xml ├── issue0576.xml ├── issue0577.xml ├── issue0578.xml ├── issue0579.xml ├── issue0580.xml ├── issue0581.xml ├── issue0582.xml ├── issue0583.xml ├── issue0584.xml ├── issue0585.xml ├── issue0586.xml ├── issue0587.xml ├── issue0588.xml ├── issue0589.xml ├── issue0590.xml ├── issue0591.xml ├── issue0592.xml ├── issue0593.xml ├── issue0594.xml ├── issue0595.xml ├── issue0596.xml ├── issue0597.xml ├── issue0598.xml ├── issue0599.xml ├── issue0600.xml ├── issue0601.xml ├── issue0602.xml ├── issue0603.xml ├── issue0604.xml ├── issue0605.xml ├── issue0606.xml ├── issue0607.xml ├── issue0608.xml ├── issue0609.xml ├── issue0610.xml ├── issue0611.xml ├── issue0612.xml ├── issue0613.xml ├── issue0614.xml ├── issue0615.xml ├── issue0616.xml ├── issue0617.xml ├── issue0618.xml ├── issue0619.xml ├── issue0620.xml ├── issue0621.xml ├── issue0622.xml ├── issue0623.xml ├── issue0624.xml ├── issue0625.xml ├── issue0626.xml ├── issue0627.xml ├── issue0628.xml ├── issue0629.xml ├── issue0630.xml ├── issue0631.xml ├── issue0632.xml ├── issue0633.xml ├── issue0634.xml ├── issue0635.xml ├── issue0636.xml ├── issue0637.xml ├── issue0638.xml ├── issue0639.xml ├── issue0640.xml ├── issue0641.xml ├── issue0642.xml ├── issue0643.xml ├── issue0644.xml ├── issue0645.xml ├── issue0646.xml ├── issue0647.xml ├── issue0648.xml ├── issue0649.xml ├── issue0650.xml ├── issue0651.xml ├── issue0652.xml ├── issue0653.xml ├── issue0654.xml ├── issue0655.xml ├── issue0656.xml ├── issue0657.xml ├── issue0658.xml ├── issue0659.xml ├── issue0660.xml ├── issue0661.xml ├── issue0662.xml ├── issue0663.xml ├── issue0664.xml ├── issue0665.xml ├── issue0666.xml ├── issue0667.xml ├── issue0668.xml ├── issue0669.xml ├── issue0670.xml ├── issue0671.xml ├── issue0672.xml ├── issue0673.xml ├── issue0674.xml ├── issue0675.xml ├── issue0676.xml ├── issue0677.xml ├── issue0678.xml ├── issue0679.xml ├── issue0680.xml ├── issue0681.xml ├── issue0682.xml ├── issue0683.xml ├── issue0684.xml ├── issue0685.xml ├── issue0686.xml ├── issue0687.xml ├── issue0688.xml ├── issue0689.xml ├── issue0690.xml ├── issue0691.xml ├── issue0692.xml ├── issue0693.xml ├── issue0694.xml ├── issue0695.xml ├── issue0696.xml ├── issue0697.xml ├── issue0698.xml ├── issue0699.xml ├── issue0700.xml ├── issue0701.xml ├── issue0702.xml ├── issue0703.xml ├── issue0704.xml ├── issue0705.xml ├── issue0706.xml ├── issue0707.xml ├── issue0708.xml ├── issue0709.xml ├── issue0710.xml ├── issue0711.xml ├── issue0712.xml ├── issue0713.xml ├── issue0714.xml ├── issue0715.xml ├── issue0716.xml ├── issue0717.xml ├── issue0718.xml ├── issue0719.xml ├── issue0720.xml ├── issue0721.xml ├── issue0722.xml ├── issue0723.xml ├── issue0724.xml ├── issue0725.xml ├── issue0726.xml ├── issue0727.xml ├── issue0728.xml ├── issue0729.xml ├── issue0730.xml ├── issue0731.xml ├── issue0732.xml ├── issue0733.xml ├── issue0734.xml ├── issue0735.xml ├── issue0736.xml ├── issue0737.xml ├── issue0738.xml ├── issue0739.xml ├── issue0740.xml ├── issue0741.xml ├── issue0742.xml ├── issue0743.xml ├── issue0744.xml ├── issue0745.xml ├── issue0746.xml ├── issue0747.xml ├── issue0748.xml ├── issue0749.xml ├── issue0750.xml ├── issue0751.xml ├── issue0752.xml ├── issue0753.xml ├── issue0754.xml ├── issue0755.xml ├── issue0756.xml ├── issue0757.xml ├── issue0758.xml ├── issue0759.xml ├── issue0760.xml ├── issue0761.xml ├── issue0762.xml ├── issue0763.xml ├── issue0764.xml ├── issue0765.xml ├── issue0766.xml ├── issue0767.xml ├── issue0768.xml ├── issue0769.xml ├── issue0770.xml ├── issue0771.xml ├── issue0772.xml ├── issue0773.xml ├── issue0774.xml ├── issue0775.xml ├── issue0776.xml ├── issue0777.xml ├── issue0778.xml ├── issue0779.xml ├── issue0780.xml ├── issue0781.xml ├── issue0782.xml ├── issue0783.xml ├── issue0784.xml ├── issue0785.xml ├── issue0786.xml ├── issue0787.xml ├── issue0788.xml ├── issue0789.xml ├── issue0790.xml ├── issue0791.xml ├── issue0792.xml ├── issue0793.xml ├── issue0794.xml ├── issue0795.xml ├── issue0796.xml ├── issue0797.xml ├── issue0798.xml ├── issue0799.xml ├── issue0800.xml ├── issue0801.xml ├── issue0802.xml ├── issue0803.xml ├── issue0804.xml ├── issue0805.xml ├── issue0806.xml ├── issue0807.xml ├── issue0808.xml ├── issue0809.xml ├── issue0810.xml ├── issue0811.xml ├── issue0812.xml ├── issue0813.xml ├── issue0814.xml ├── issue0815.xml ├── issue0816.xml ├── issue0817.xml ├── issue0818.xml ├── issue0819.xml ├── issue0820.xml ├── issue0821.xml ├── issue0822.xml ├── issue0823.xml ├── issue0824.xml ├── issue0825.xml ├── issue0826.xml ├── issue0827.xml ├── issue0828.xml ├── issue0829.xml ├── issue0830.xml ├── issue0831.xml ├── issue0832.xml ├── issue0833.xml ├── issue0834.xml ├── issue0835.xml ├── issue0836.xml ├── issue0837.xml ├── issue0838.xml ├── issue0839.xml ├── issue0840.xml ├── issue0841.xml ├── issue0842.xml ├── issue0843.xml ├── issue0844.xml ├── issue0845.xml ├── issue0846.xml ├── issue0847.xml ├── issue0848.xml ├── issue0849.xml ├── issue0850.xml ├── issue0851.xml ├── issue0852.xml ├── issue0853.xml ├── issue0854.xml ├── issue0855.xml ├── issue0856.xml ├── issue0857.xml ├── issue0858.xml ├── issue0859.xml ├── issue0860.xml ├── issue0861.xml ├── issue0862.xml ├── issue0863.xml ├── issue0864.xml ├── issue0865.xml ├── issue0866.xml ├── issue0867.xml ├── issue0868.xml ├── issue0869.xml ├── issue0870.xml ├── issue0871.xml ├── issue0872.xml ├── issue0873.xml ├── issue0874.xml ├── issue0875.xml ├── issue0876.xml ├── issue0877.xml ├── issue0878.xml ├── issue0879.xml ├── issue0880.xml ├── issue0881.xml ├── issue0882.xml ├── issue0883.xml ├── issue0884.xml ├── issue0885.xml ├── issue0886.xml ├── issue0887.xml ├── issue0888.xml ├── issue0889.xml ├── issue0890.xml ├── issue0891.xml ├── issue0892.xml ├── issue0893.xml ├── issue0894.xml ├── issue0895.xml ├── issue0896.xml ├── issue0897.xml ├── issue0898.xml ├── issue0899.xml ├── issue0900.xml ├── issue0901.xml ├── issue0902.xml ├── issue0903.xml ├── issue0904.xml ├── issue0905.xml ├── issue0906.xml ├── issue0907.xml ├── issue0908.xml ├── issue0909.xml ├── issue0910.xml ├── issue0911.xml ├── issue0912.xml ├── issue0913.xml ├── issue0914.xml ├── issue0915.xml ├── issue0916.xml ├── issue0917.xml ├── issue0918.xml ├── issue0919.xml ├── issue0920.xml ├── issue0921.xml ├── issue0922.xml ├── issue0923.xml ├── issue0924.xml ├── issue0925.xml ├── issue0926.xml ├── issue0927.xml ├── issue0928.xml ├── issue0929.xml ├── issue0930.xml ├── issue0931.xml ├── issue0932.xml ├── issue0933.xml ├── issue0934.xml ├── issue0935.xml ├── issue0936.xml ├── issue0937.xml ├── issue0938.xml ├── issue0939.xml ├── issue0940.xml ├── issue0941.xml ├── issue0942.xml ├── issue0943.xml ├── issue0944.xml ├── issue0945.xml ├── issue0946.xml ├── issue0947.xml ├── issue0948.xml ├── issue0949.xml ├── issue0950.xml ├── issue0951.xml ├── issue0952.xml ├── issue0953.xml ├── issue0954.xml ├── issue0955.xml ├── issue0956.xml ├── issue0957.xml ├── issue0958.xml ├── issue0959.xml ├── issue0960.xml ├── issue0961.xml ├── issue0962.xml ├── issue0963.xml ├── issue0964.xml ├── issue0965.xml ├── issue0966.xml ├── issue0967.xml ├── issue0968.xml ├── issue0969.xml ├── issue0970.xml ├── issue0971.xml ├── issue0972.xml ├── issue0973.xml ├── issue0974.xml ├── issue0975.xml ├── issue0976.xml ├── issue0977.xml ├── issue0978.xml ├── issue0979.xml ├── issue0980.xml ├── issue0981.xml ├── issue0982.xml ├── issue0983.xml ├── issue0984.xml ├── issue0985.xml ├── issue0986.xml ├── issue0987.xml ├── issue0988.xml ├── issue0989.xml ├── issue0990.xml ├── issue0991.xml ├── issue0992.xml ├── issue0993.xml ├── issue0994.xml ├── issue0995.xml ├── issue0996.xml ├── issue0997.xml ├── issue0998.xml ├── issue0999.xml ├── issue1000.xml ├── issue1001.xml ├── issue1002.xml ├── issue1003.xml ├── issue1004.xml ├── issue1005.xml ├── issue1006.xml ├── issue1007.xml ├── issue1008.xml ├── issue1009.xml ├── issue1010.xml ├── issue1011.xml ├── issue1012.xml ├── issue1013.xml ├── issue1014.xml ├── issue1015.xml ├── issue1016.xml ├── issue1017.xml ├── issue1018.xml ├── issue1019.xml ├── issue1020.xml ├── issue1021.xml ├── issue1022.xml ├── issue1023.xml ├── issue1024.xml ├── issue1025.xml ├── issue1026.xml ├── issue1027.xml ├── issue1028.xml ├── issue1029.xml ├── issue1030.xml ├── issue1031.xml ├── issue1032.xml ├── issue1033.xml ├── issue1034.xml ├── issue1035.xml ├── issue1036.xml ├── issue1037.xml ├── issue1038.xml ├── issue1039.xml ├── issue1040.xml ├── issue1041.xml ├── issue1042.xml ├── issue1043.xml ├── issue1044.xml ├── issue1045.xml ├── issue1046.xml ├── issue1047.xml ├── issue1048.xml ├── issue1049.xml ├── issue1050.xml ├── issue1051.xml ├── issue1052.xml ├── issue1053.xml ├── issue1054.xml ├── issue1055.xml ├── issue1056.xml ├── issue1057.xml ├── issue1058.xml ├── issue1059.xml ├── issue1060.xml ├── issue1061.xml ├── issue1062.xml ├── issue1063.xml ├── issue1064.xml ├── issue1065.xml ├── issue1066.xml ├── issue1067.xml ├── issue1068.xml ├── issue1069.xml ├── issue1070.xml ├── issue1071.xml ├── issue1072.xml ├── issue1073.xml ├── issue1074.xml ├── issue1075.xml ├── issue1076.xml ├── issue1077.xml ├── issue1078.xml ├── issue1079.xml ├── issue1080.xml ├── issue1081.xml ├── issue1082.xml ├── issue1083.xml ├── issue1084.xml ├── issue1085.xml ├── issue1086.xml ├── issue1087.xml ├── issue1088.xml ├── issue1089.xml ├── issue1090.xml ├── issue1091.xml ├── issue1092.xml ├── issue1093.xml ├── issue1094.xml ├── issue1095.xml ├── issue1096.xml ├── issue1097.xml ├── issue1098.xml ├── issue1099.xml ├── issue1100.xml ├── issue1101.xml ├── issue1102.xml ├── issue1103.xml ├── issue1104.xml ├── issue1105.xml ├── issue1106.xml ├── issue1107.xml ├── issue1108.xml ├── issue1109.xml ├── issue1110.xml ├── issue1111.xml ├── issue1112.xml ├── issue1113.xml ├── issue1114.xml ├── issue1115.xml ├── issue1116.xml ├── issue1117.xml ├── issue1118.xml ├── issue1119.xml ├── issue1120.xml ├── issue1121.xml ├── issue1122.xml ├── issue1123.xml ├── issue1124.xml ├── issue1125.xml ├── issue1126.xml ├── issue1127.xml ├── issue1128.xml ├── issue1129.xml ├── issue1130.xml ├── issue1131.xml ├── issue1132.xml ├── issue1133.xml ├── issue1134.xml ├── issue1135.xml ├── issue1136.xml ├── issue1137.xml ├── issue1138.xml ├── issue1139.xml ├── issue1140.xml ├── issue1141.xml ├── issue1142.xml ├── issue1143.xml ├── issue1144.xml ├── issue1145.xml ├── issue1146.xml ├── issue1147.xml ├── issue1148.xml ├── issue1149.xml ├── issue1150.xml ├── issue1151.xml ├── issue1152.xml ├── issue1153.xml ├── issue1154.xml ├── issue1155.xml ├── issue1156.xml ├── issue1157.xml ├── issue1158.xml ├── issue1159.xml ├── issue1160.xml ├── issue1161.xml ├── issue1162.xml ├── issue1163.xml ├── issue1164.xml ├── issue1165.xml ├── issue1166.xml ├── issue1167.xml ├── issue1168.xml ├── issue1169.xml ├── issue1170.xml ├── issue1171.xml ├── issue1172.xml ├── issue1173.xml ├── issue1174.xml ├── issue1175.xml ├── issue1176.xml ├── issue1177.xml ├── issue1178.xml ├── issue1179.xml ├── issue1180.xml ├── issue1181.xml ├── issue1182.xml ├── issue1183.xml ├── issue1184.xml ├── issue1185.xml ├── issue1186.xml ├── issue1187.xml ├── issue1188.xml ├── issue1189.xml ├── issue1190.xml ├── issue1191.xml ├── issue1192.xml ├── issue1193.xml ├── issue1194.xml ├── issue1195.xml ├── issue1196.xml ├── issue1197.xml ├── issue1198.xml ├── issue1199.xml ├── issue1200.xml ├── issue1201.xml ├── issue1202.xml ├── issue1203.xml ├── issue1204.xml ├── issue1205.xml ├── issue1206.xml ├── issue1207.xml ├── issue1208.xml ├── issue1209.xml ├── issue1210.xml ├── issue1211.xml ├── issue1212.xml ├── issue1213.xml ├── issue1214.xml ├── issue1215.xml ├── issue1216.xml ├── issue1217.xml ├── issue1218.xml ├── issue1219.xml ├── issue1220.xml ├── issue1221.xml ├── issue1222.xml ├── issue1223.xml ├── issue1224.xml ├── issue1225.xml ├── issue1226.xml ├── issue1227.xml ├── issue1228.xml ├── issue1229.xml ├── issue1230.xml ├── issue1231.xml ├── issue1232.xml ├── issue1233.xml ├── issue1234.xml ├── issue1235.xml ├── issue1236.xml ├── issue1237.xml ├── issue1238.xml ├── issue1239.xml ├── issue1240.xml ├── issue1241.xml ├── issue1242.xml ├── issue1243.xml ├── issue1244.xml ├── issue1245.xml ├── issue1246.xml ├── issue1247.xml ├── issue1248.xml ├── issue1249.xml ├── issue1250.xml ├── issue1251.xml ├── issue1252.xml ├── issue1253.xml ├── issue1254.xml ├── issue1255.xml ├── issue1256.xml ├── issue1257.xml ├── issue1258.xml ├── issue1259.xml ├── issue1260.xml ├── issue1261.xml ├── issue1262.xml ├── issue1263.xml ├── issue1264.xml ├── issue1265.xml ├── issue1266.xml ├── issue1267.xml ├── issue1268.xml ├── issue1269.xml ├── issue1270.xml ├── issue1271.xml ├── issue1272.xml ├── issue1273.xml ├── issue1274.xml ├── issue1275.xml ├── issue1276.xml ├── issue1277.xml ├── issue1278.xml ├── issue1279.xml ├── issue1280.xml ├── issue1281.xml ├── issue1282.xml ├── issue1283.xml ├── issue1284.xml ├── issue1285.xml ├── issue1286.xml ├── issue1287.xml ├── issue1288.xml ├── issue1289.xml ├── issue1290.xml ├── issue1291.xml ├── issue1292.xml ├── issue1293.xml ├── issue1294.xml ├── issue1295.xml ├── issue1296.xml ├── issue1297.xml ├── issue1298.xml ├── issue1299.xml ├── issue1300.xml ├── issue1301.xml ├── issue1302.xml ├── issue1303.xml ├── issue1304.xml ├── issue1305.xml ├── issue1306.xml ├── issue1307.xml ├── issue1308.xml ├── issue1309.xml ├── issue1310.xml ├── issue1311.xml ├── issue1312.xml ├── issue1313.xml ├── issue1314.xml ├── issue1315.xml ├── issue1316.xml ├── issue1317.xml ├── issue1318.xml ├── issue1319.xml ├── issue1320.xml ├── issue1321.xml ├── issue1322.xml ├── issue1323.xml ├── issue1324.xml ├── issue1325.xml ├── issue1326.xml ├── issue1327.xml ├── issue1328.xml ├── issue1329.xml ├── issue1330.xml ├── issue1331.xml ├── issue1332.xml ├── issue1333.xml ├── issue1334.xml ├── issue1335.xml ├── issue1337.xml ├── issue1338.xml ├── issue1339.xml ├── issue1340.xml ├── issue1344.xml ├── issue1345.xml ├── issue1346.xml ├── issue1347.xml ├── issue1348.xml ├── issue1349.xml ├── issue1350.xml ├── issue1351.xml ├── issue1352.xml ├── issue1353.xml ├── issue1354.xml ├── issue1355.xml ├── issue1356.xml ├── issue1357.xml ├── issue1358.xml ├── issue1359.xml ├── issue1360.xml ├── issue1361.xml ├── issue1362.xml ├── issue1363.xml ├── issue1364.xml ├── issue1365.xml ├── issue1366.xml ├── issue1367.xml ├── issue1368.xml ├── issue1369.xml ├── issue1370.xml ├── issue1371.xml ├── issue1372.xml ├── issue1373.xml ├── issue1374.xml ├── issue1375.xml ├── issue1376.xml ├── issue1377.xml ├── issue1378.xml ├── issue1379.xml ├── issue1380.xml ├── issue1381.xml ├── issue1382.xml ├── issue1383.xml ├── issue1384.xml ├── issue1385.xml ├── issue1386.xml ├── issue1387.xml ├── issue1388.xml ├── issue1389.xml ├── issue1390.xml ├── issue1391.xml ├── issue1392.xml ├── issue1393.xml ├── issue1394.xml ├── issue1395.xml ├── issue1396.xml ├── issue1397.xml ├── issue1398.xml ├── issue1399.xml ├── issue1400.xml ├── issue1401.xml ├── issue1402.xml ├── issue1403.xml ├── issue1404.xml ├── issue1405.xml ├── issue1406.xml ├── issue1407.xml ├── issue1408.xml ├── issue1409.xml ├── issue1410.xml ├── issue1411.xml ├── issue1412.xml ├── issue1413.xml ├── issue1414.xml ├── issue1415.xml ├── issue1416.xml ├── issue1417.xml ├── issue1418.xml ├── issue1419.xml ├── issue1420.xml ├── issue1421.xml ├── issue1422.xml ├── issue1423.xml ├── issue1424.xml ├── issue1425.xml ├── issue1426.xml ├── issue1427.xml ├── issue1428.xml ├── issue1429.xml ├── issue1430.xml ├── issue1431.xml ├── issue1432.xml ├── issue1433.xml ├── issue1434.xml ├── issue1435.xml ├── issue1436.xml ├── issue1437.xml ├── issue1438.xml ├── issue1439.xml ├── issue1440.xml ├── issue1441.xml ├── issue1442.xml ├── issue1443.xml ├── issue1444.xml ├── issue1445.xml ├── issue1446.xml ├── issue1447.xml ├── issue1448.xml ├── issue1449.xml ├── issue1450.xml ├── issue1451.xml ├── issue1452.xml ├── issue1453.xml ├── issue1454.xml ├── issue1455.xml ├── issue1456.xml ├── issue1457.xml ├── issue1458.xml ├── issue1459.xml ├── issue1460.xml ├── issue1461.xml ├── issue1462.xml ├── issue1463.xml ├── issue1464.xml ├── issue1465.xml ├── issue1466.xml ├── issue1467.xml ├── issue1468.xml ├── issue1469.xml ├── issue1470.xml ├── issue1471.xml ├── issue1472.xml ├── issue1473.xml ├── issue1474.xml ├── issue1475.xml ├── issue1476.xml ├── issue1477.xml ├── issue1478.xml ├── issue1479.xml ├── issue1480.xml ├── issue1481.xml ├── issue1482.xml ├── issue1483.xml ├── issue1484.xml ├── issue1485.xml ├── issue1486.xml ├── issue1487.xml ├── issue1488.xml ├── issue1489.xml ├── issue1490.xml ├── issue1491.xml ├── issue1492.xml ├── issue1493.xml ├── issue1494.xml ├── issue1495.xml ├── issue1496.xml ├── issue1497.xml ├── issue1498.xml ├── issue1499.xml ├── issue1500.xml ├── issue1501.xml ├── issue1502.xml ├── issue1503.xml ├── issue1504.xml ├── issue1505.xml ├── issue1506.xml ├── issue1507.xml ├── issue1508.xml ├── issue1509.xml ├── issue1510.xml ├── issue1511.xml ├── issue1512.xml ├── issue1513.xml ├── issue1514.xml ├── issue1515.xml ├── issue1516.xml ├── issue1517.xml ├── issue1518.xml ├── issue1519.xml ├── issue1520.xml ├── issue1521.xml ├── issue1522.xml ├── issue1523.xml ├── issue1524.xml ├── issue1525.xml ├── issue1526.xml ├── issue2000.xml ├── issue2001.xml ├── issue2002.xml ├── issue2003.xml ├── issue2004.xml ├── issue2005.xml ├── issue2006.xml ├── issue2007.xml ├── issue2008.xml ├── issue2009.xml ├── issue2010.xml ├── issue2011.xml ├── issue2012.xml ├── issue2013.xml ├── issue2014.xml ├── issue2015.xml ├── issue2016.xml ├── issue2017.xml ├── issue2018.xml ├── issue2019.xml ├── issue2020.xml ├── issue2021.xml ├── issue2022.xml ├── issue2023.xml ├── issue2024.xml ├── issue2025.xml ├── issue2026.xml ├── issue2027.xml ├── issue2028.xml ├── issue2029.xml ├── issue2030.xml ├── issue2031.xml ├── issue2032.xml ├── issue2033.xml ├── issue2034.xml ├── issue2035.xml ├── issue2036.xml ├── issue2037.xml ├── issue2038.xml ├── issue2039.xml ├── issue2040.xml ├── issue2041.xml ├── issue2042.xml ├── issue2043.xml ├── issue2044.xml ├── issue2045.xml ├── issue2046.xml ├── issue2047.xml ├── issue2048.xml ├── issue2049.xml ├── issue2050.xml ├── issue2051.xml ├── issue2052.xml ├── issue2053.xml ├── issue2054.xml ├── issue2055.xml ├── issue2056.xml ├── issue2057.xml ├── issue2058.xml ├── issue2059.xml ├── issue2060.xml ├── issue2061.xml ├── issue2062.xml ├── issue2063.xml ├── issue2064.xml ├── issue2065.xml ├── issue2066.xml ├── issue2067.xml ├── issue2068.xml ├── issue2069.xml ├── issue2070.xml ├── issue2071.xml ├── issue2072.xml ├── issue2073.xml ├── issue2074.xml ├── issue2075.xml ├── issue2076.xml ├── issue2077.xml ├── issue2078.xml ├── issue2079.xml ├── issue2080.xml ├── issue2081.xml ├── issue2082.xml ├── issue2083.xml ├── issue2084.xml ├── issue2085.xml ├── issue2086.xml ├── issue2087.xml ├── issue2088.xml ├── issue2089.xml ├── issue2090.xml ├── issue2091.xml ├── issue2092.xml ├── issue2093.xml ├── issue2094.xml ├── issue2095.xml ├── issue2096.xml ├── issue2097.xml ├── issue2098.xml ├── issue2099.xml ├── issue2100.xml ├── issue2101.xml ├── issue2102.xml ├── issue2103.xml ├── issue2104.xml ├── issue2105.xml ├── issue2106.xml ├── issue2107.xml ├── issue2108.xml ├── issue2109.xml ├── issue2110.xml ├── issue2111.xml ├── issue2112.xml ├── issue2113.xml ├── issue2114.xml ├── issue2115.xml ├── issue2116.xml ├── issue2117.xml ├── issue2118.xml ├── issue2119.xml ├── issue2120.xml ├── issue2121.xml ├── issue2122.xml ├── issue2123.xml ├── issue2124.xml ├── issue2125.xml ├── issue2126.xml ├── issue2127.xml ├── issue2128.xml ├── issue2129.xml ├── issue2130.xml ├── issue2131.xml ├── issue2132.xml ├── issue2133.xml ├── issue2134.xml ├── issue2135.xml ├── issue2136.xml ├── issue2137.xml ├── issue2138.xml ├── issue2139.xml ├── issue2140.xml ├── issue2141.xml ├── issue2142.xml ├── issue2143.xml ├── issue2144.xml ├── issue2145.xml ├── issue2146.xml ├── issue2147.xml ├── issue2148.xml ├── issue2149.xml ├── issue2150.xml ├── issue2151.xml ├── issue2152.xml ├── issue2153.xml ├── issue2154.xml ├── issue2155.xml ├── issue2156.xml ├── issue2157.xml ├── issue2158.xml ├── issue2159.xml ├── issue2160.xml ├── issue2161.xml ├── issue2162.xml ├── issue2163.xml ├── issue2164.xml ├── issue2165.xml ├── issue2166.xml ├── issue2167.xml ├── issue2168.xml ├── issue2169.xml ├── issue2170.xml ├── issue2171.xml ├── issue2172.xml ├── issue2173.xml ├── issue2174.xml ├── issue2175.xml ├── issue2176.xml ├── issue2177.xml ├── issue2178.xml ├── issue2179.xml ├── issue2180.xml ├── issue2181.xml ├── issue2182.xml ├── issue2183.xml ├── issue2184.xml ├── issue2185.xml ├── issue2186.xml ├── issue2187.xml ├── issue2188.xml ├── issue2189.xml ├── issue2190.xml ├── issue2191.xml ├── issue2192.xml ├── issue2193.xml ├── issue2194.xml ├── issue2195.xml ├── issue2196.xml ├── issue2197.xml ├── issue2198.xml ├── issue2199.xml ├── issue2200.xml ├── issue2201.xml ├── issue2202.xml ├── issue2203.xml ├── issue2204.xml ├── issue2205.xml ├── issue2206.xml ├── issue2207.xml ├── issue2208.xml ├── issue2209.xml ├── issue2210.xml ├── issue2211.xml ├── issue2212.xml ├── issue2213.xml ├── issue2214.xml ├── issue2215.xml ├── issue2216.xml ├── issue2217.xml ├── issue2218.xml ├── issue2219.xml ├── issue2220.xml ├── issue2221.xml ├── issue2222.xml ├── issue2223.xml ├── issue2224.xml ├── issue2225.xml ├── issue2226.xml ├── issue2227.xml ├── issue2228.xml ├── issue2229.xml ├── issue2230.xml ├── issue2231.xml ├── issue2232.xml ├── issue2233.xml ├── issue2234.xml ├── issue2235.xml ├── issue2236.xml ├── issue2237.xml ├── issue2238.xml ├── issue2239.xml ├── issue2240.xml ├── issue2241.xml ├── issue2242.xml ├── issue2243.xml ├── issue2244.xml ├── issue2245.xml ├── issue2246.xml ├── issue2247.xml ├── issue2248.xml ├── issue2249.xml ├── issue2250.xml ├── issue2251.xml ├── issue2252.xml ├── issue2253.xml ├── issue2254.xml ├── issue2255.xml ├── issue2256.xml ├── issue2257.xml ├── issue2258.xml ├── issue2259.xml ├── issue2260.xml ├── issue2261.xml ├── issue2262.xml ├── issue2263.xml ├── issue2264.xml ├── issue2265.xml ├── issue2266.xml ├── issue2267.xml ├── issue2268.xml ├── issue2269.xml ├── issue2270.xml ├── issue2271.xml ├── issue2272.xml ├── issue2273.xml ├── issue2274.xml ├── issue2275.xml ├── issue2276.xml ├── issue2277.xml ├── issue2278.xml ├── issue2279.xml ├── issue2280.xml ├── issue2281.xml ├── issue2282.xml ├── issue2283.xml ├── issue2284.xml ├── issue2285.xml ├── issue2286.xml ├── issue2287.xml ├── issue2288.xml ├── issue2289.xml ├── issue2290.xml ├── issue2291.xml ├── issue2292.xml ├── issue2293.xml ├── issue2294.xml ├── issue2295.xml ├── issue2296.xml ├── issue2297.xml ├── issue2298.xml ├── issue2299.xml ├── issue2300.xml ├── issue2301.xml ├── issue2302.xml ├── issue2303.xml ├── issue2304.xml ├── issue2305.xml ├── issue2306.xml ├── issue2307.xml ├── issue2308.xml ├── issue2309.xml ├── issue2310.xml ├── issue2311.xml ├── issue2312.xml ├── issue2313.xml ├── issue2314.xml ├── issue2315.xml ├── issue2316.xml ├── issue2317.xml ├── issue2318.xml ├── issue2319.xml ├── issue2320.xml ├── issue2321.xml ├── issue2322.xml ├── issue2323.xml ├── issue2324.xml ├── issue2325.xml ├── issue2326.xml ├── issue2327.xml ├── issue2328.xml ├── issue2329.xml ├── issue2330.xml ├── issue2331.xml ├── issue2332.xml ├── issue2333.xml ├── issue2334.xml ├── issue2335.xml ├── issue2336.xml ├── issue2337.xml ├── issue2338.xml ├── issue2339.xml ├── issue2340.xml ├── issue2341.xml ├── issue2342.xml ├── issue2343.xml ├── issue2344.xml ├── issue2345.xml ├── issue2346.xml ├── issue2347.xml ├── issue2348.xml ├── issue2349.xml ├── issue2350.xml ├── issue2351.xml ├── issue2352.xml ├── issue2353.xml ├── issue2354.xml ├── issue2355.xml ├── issue2356.xml ├── issue2357.xml ├── issue2358.xml ├── issue2359.xml ├── issue2360.xml ├── issue2361.xml ├── issue2362.xml ├── issue2363.xml ├── issue2364.xml ├── issue2365.xml ├── issue2366.xml ├── issue2367.xml ├── issue2368.xml ├── issue2369.xml ├── issue2370.xml ├── issue2371.xml ├── issue2372.xml ├── issue2373.xml ├── issue2374.xml ├── issue2375.xml ├── issue2376.xml ├── issue2377.xml ├── issue2378.xml ├── issue2379.xml ├── issue2380.xml ├── issue2381.xml ├── issue2382.xml ├── issue2383.xml ├── issue2384.xml ├── issue2385.xml ├── issue2386.xml ├── issue2387.xml ├── issue2388.xml ├── issue2389.xml ├── issue2390.xml ├── issue2391.xml ├── issue2392.xml ├── issue2393.xml ├── issue2394.xml ├── issue2395.xml ├── issue2396.xml ├── issue2397.xml ├── issue2398.xml ├── issue2399.xml ├── issue2400.xml ├── issue2401.xml ├── issue2402.xml ├── issue2403.xml ├── issue2404.xml ├── issue2405.xml ├── issue2406.xml ├── issue2407.xml ├── issue2408.xml ├── issue2409.xml ├── issue2410.xml ├── issue2411.xml ├── issue2412.xml ├── issue2413.xml ├── issue2414.xml ├── issue2415.xml ├── issue2416.xml ├── issue2417.xml ├── issue2418.xml ├── issue2419.xml ├── issue2420.xml ├── issue2421.xml ├── issue2422.xml ├── issue2423.xml ├── issue2424.xml ├── issue2425.xml ├── issue2426.xml ├── issue2427.xml ├── issue2428.xml ├── issue2429.xml ├── issue2430.xml ├── issue2431.xml ├── issue2432.xml ├── issue2433.xml ├── issue2434.xml ├── issue2435.xml ├── issue2436.xml ├── issue2437.xml ├── issue2438.xml ├── issue2439.xml ├── issue2440.xml ├── issue2441.xml ├── issue2442.xml ├── issue2443.xml ├── issue2444.xml ├── issue2445.xml ├── issue2446.xml ├── issue2447.xml ├── issue2448.xml ├── issue2449.xml ├── issue2450.xml ├── issue2451.xml ├── issue2452.xml ├── issue2453.xml ├── issue2454.xml ├── issue2455.xml ├── issue2456.xml ├── issue2457.xml ├── issue2458.xml ├── issue2459.xml ├── issue2460.xml ├── issue2461.xml ├── issue2462.xml ├── issue2463.xml ├── issue2464.xml ├── issue2465.xml ├── issue2466.xml ├── issue2467.xml ├── issue2468.xml ├── issue2469.xml ├── issue2470.xml ├── issue2471.xml ├── issue2472.xml ├── issue2473.xml ├── issue2474.xml ├── issue2475.xml ├── issue2476.xml ├── issue2477.xml ├── issue2478.xml ├── issue2479.xml ├── issue2480.xml ├── issue2481.xml ├── issue2482.xml ├── issue2483.xml ├── issue2484.xml ├── issue2485.xml ├── issue2486.xml ├── issue2487.xml ├── issue2488.xml ├── issue2489.xml ├── issue2490.xml ├── issue2491.xml ├── issue2492.xml ├── issue2493.xml ├── issue2494.xml ├── issue2495.xml ├── issue2496.xml ├── issue2497.xml ├── issue2498.xml ├── issue2499.xml ├── issue2500.xml ├── issue2501.xml ├── issue2502.xml ├── issue2503.xml ├── issue2504.xml ├── issue2505.xml ├── issue2506.xml ├── issue2507.xml ├── issue2508.xml ├── issue2509.xml ├── issue2510.xml ├── issue2511.xml ├── issue2512.xml ├── issue2513.xml ├── issue2514.xml ├── issue2515.xml ├── issue2516.xml ├── issue2517.xml ├── issue2518.xml ├── issue2519.xml ├── issue2520.xml ├── issue2521.xml ├── issue2522.xml ├── issue2523.xml ├── issue2524.xml ├── issue2525.xml ├── issue2526.xml ├── issue2527.xml ├── issue2528.xml ├── issue2529.xml ├── issue2530.xml ├── issue2531.xml ├── issue2532.xml ├── issue2533.xml ├── issue2534.xml ├── issue2535.xml ├── issue2536.xml ├── issue2537.xml ├── issue2538.xml ├── issue2539.xml ├── issue2540.xml ├── issue2541.xml ├── issue2542.xml ├── issue2543.xml ├── issue2544.xml ├── issue2545.xml ├── issue2546.xml ├── issue2547.xml ├── issue2548.xml ├── issue2549.xml ├── issue2550.xml ├── issue2551.xml ├── issue2552.xml ├── issue2553.xml ├── issue2554.xml ├── issue2555.xml ├── issue2556.xml ├── issue2557.xml ├── issue2558.xml ├── issue2559.xml ├── issue2560.xml ├── issue2561.xml ├── issue2562.xml ├── issue2563.xml ├── issue2564.xml ├── issue2565.xml ├── issue2566.xml ├── issue2567.xml ├── issue2568.xml ├── issue2569.xml ├── issue2570.xml ├── issue2571.xml ├── issue2572.xml ├── issue2573.xml ├── issue2574.xml ├── issue2575.xml ├── issue2576.xml ├── issue2577.xml ├── issue2578.xml ├── issue2579.xml ├── issue2580.xml ├── issue2581.xml ├── issue2582.xml ├── issue2583.xml ├── issue2584.xml ├── issue2585.xml ├── issue2586.xml ├── issue2587.xml ├── issue2588.xml ├── issue2589.xml ├── issue2590.xml ├── issue2591.xml ├── issue2592.xml ├── issue2593.xml ├── issue2594.xml ├── issue2595.xml ├── issue2596.xml ├── issue2597.xml ├── issue2598.xml ├── issue2599.xml ├── issue2600.xml ├── issue2601.xml ├── issue2602.xml ├── issue2603.xml ├── issue2604.xml ├── issue2605.xml ├── issue2606.xml ├── issue2607.xml ├── issue2608.xml ├── issue2609.xml ├── issue2610.xml ├── issue2611.xml ├── issue2612.xml ├── issue2613.xml ├── issue2614.xml ├── issue2615.xml ├── issue2616.xml ├── issue2617.xml ├── issue2618.xml ├── issue2619.xml ├── issue2621.xml ├── issue2622.xml ├── issue2623.xml ├── issue2624.xml ├── issue2625.xml ├── issue2626.xml ├── issue2627.xml ├── issue2628.xml ├── issue2629.xml ├── issue2630.xml ├── issue2631.xml ├── issue2632.xml ├── issue2633.xml ├── issue2634.xml ├── issue2635.xml ├── issue2636.xml ├── issue2637.xml ├── issue2638.xml ├── issue2639.xml ├── issue2640.xml ├── issue2641.xml ├── issue2642.xml ├── issue2643.xml ├── issue2644.xml ├── issue2645.xml ├── issue2646.xml ├── issue2647.xml ├── issue2648.xml ├── issue2649.xml ├── issue2650.xml ├── issue2651.xml ├── issue2652.xml ├── issue2653.xml ├── issue2654.xml ├── issue2655.xml ├── issue2656.xml ├── issue2657.xml ├── issue2658.xml ├── issue2659.xml ├── issue2660.xml ├── issue2661.xml ├── issue2662.xml ├── issue2663.xml ├── issue2664.xml ├── issue2665.xml ├── issue2666.xml ├── issue2667.xml ├── issue2668.xml ├── issue2669.xml ├── issue2670.xml ├── issue2671.xml ├── issue2672.xml ├── issue2673.xml ├── issue2674.xml ├── issue2675.xml ├── issue2676.xml ├── issue2677.xml ├── issue2678.xml ├── issue2679.xml ├── issue2680.xml ├── issue2681.xml ├── issue2682.xml ├── issue2683.xml ├── issue2684.xml ├── issue2685.xml ├── issue2686.xml ├── issue2687.xml ├── issue2688.xml ├── issue2689.xml ├── issue2690.xml ├── issue2691.xml ├── issue2692.xml ├── issue2693.xml ├── issue2694.xml ├── issue2695.xml ├── issue2696.xml ├── issue2697.xml ├── issue2698.xml ├── issue2699.xml ├── issue2700.xml ├── issue2701.xml ├── issue2702.xml ├── issue2703.xml ├── issue2704.xml ├── issue2705.xml ├── issue2706.xml ├── issue2707.xml ├── issue2708.xml ├── issue2709.xml ├── issue2710.xml ├── issue2711.xml ├── issue2712.xml ├── issue2713.xml ├── issue2714.xml ├── issue2715.xml ├── issue2716.xml ├── issue2717.xml ├── issue2718.xml ├── issue2719.xml ├── issue2720.xml ├── issue2721.xml ├── issue2722.xml ├── issue2723.xml ├── issue2724.xml ├── issue2725.xml ├── issue2726.xml ├── issue2727.xml ├── issue2728.xml ├── issue2729.xml ├── issue2730.xml ├── issue2731.xml ├── issue2732.xml ├── issue2733.xml ├── issue2734.xml ├── issue2735.xml ├── issue2736.xml ├── issue2737.xml ├── issue2738.xml ├── issue2739.xml ├── issue2740.xml ├── issue2741.xml ├── issue2742.xml ├── issue2743.xml ├── issue2744.xml ├── issue2745.xml ├── issue2746.xml ├── issue2747.xml ├── issue2748.xml ├── issue2749.xml ├── issue2750.xml ├── issue2751.xml ├── issue2752.xml ├── issue2753.xml ├── issue2754.xml ├── issue2755.xml ├── issue2756.xml ├── issue2757.xml ├── issue2758.xml ├── issue2759.xml ├── issue2760.xml ├── issue2761.xml ├── issue2762.xml ├── issue2763.xml ├── issue2764.xml ├── issue2765.xml ├── issue2766.xml ├── issue2767.xml ├── issue2768.xml ├── issue2769.xml ├── issue2770.xml ├── issue2771.xml ├── issue2772.xml ├── issue2773.xml ├── issue2774.xml ├── issue2775.xml ├── issue2776.xml ├── issue2777.xml ├── issue2778.xml ├── issue2779.xml ├── issue2780.xml ├── issue2781.xml ├── issue2782.xml ├── issue2783.xml ├── issue2784.xml ├── issue2785.xml ├── issue2786.xml ├── issue2787.xml ├── issue2788.xml ├── issue2789.xml ├── issue2790.xml ├── issue2791.xml ├── issue2792.xml ├── issue2793.xml ├── issue2794.xml ├── issue2795.xml ├── issue2796.xml ├── issue2797.xml ├── issue2798.xml ├── issue2799.xml ├── issue2800.xml ├── issue2801.xml ├── issue2802.xml ├── issue2803.xml ├── issue2804.xml ├── issue2805.xml ├── issue2806.xml ├── issue2807.xml ├── issue2808.xml ├── issue2809.xml ├── issue2810.xml ├── issue2811.xml ├── issue2812.xml ├── issue2813.xml ├── issue2814.xml ├── issue2815.xml ├── issue2816.xml ├── issue2817.xml ├── issue2818.xml ├── issue2819.xml ├── issue2820.xml ├── issue2821.xml ├── issue2822.xml ├── issue2823.xml ├── issue2824.xml ├── issue2825.xml ├── issue2826.xml ├── issue2827.xml ├── issue2828.xml ├── issue2829.xml ├── issue2830.xml ├── issue2831.xml ├── issue2832.xml ├── issue2833.xml ├── issue2834.xml ├── issue2835.xml ├── issue2836.xml ├── issue2837.xml ├── issue2838.xml ├── issue2839.xml ├── issue2840.xml ├── issue2841.xml ├── issue2842.xml ├── issue2843.xml ├── issue2844.xml ├── issue2845.xml ├── issue2846.xml ├── issue2847.xml ├── issue2848.xml ├── issue2849.xml ├── issue2850.xml ├── issue2851.xml ├── issue2852.xml ├── issue2853.xml ├── issue2854.xml ├── issue2855.xml ├── issue2856.xml ├── issue2857.xml ├── issue2858.xml ├── issue2859.xml ├── issue2860.xml ├── issue2861.xml ├── issue2862.xml ├── issue2863.xml ├── issue2864.xml ├── issue2865.xml ├── issue2866.xml ├── issue2867.xml ├── issue2868.xml ├── issue2869.xml ├── issue2870.xml ├── issue2871.xml ├── issue2872.xml ├── issue2873.xml ├── issue2874.xml ├── issue2875.xml ├── issue2876.xml ├── issue2877.xml ├── issue2878.xml ├── issue2879.xml ├── issue2880.xml ├── issue2881.xml ├── issue2882.xml ├── issue2883.xml ├── issue2884.xml ├── issue2885.xml ├── issue2886.xml ├── issue2887.xml ├── issue2888.xml ├── issue2889.xml ├── issue2890.xml ├── issue2891.xml ├── issue2892.xml ├── issue2893.xml ├── issue2894.xml ├── issue2895.xml ├── issue2896.xml ├── issue2897.xml ├── issue2898.xml ├── issue2899.xml ├── issue2900.xml ├── issue2901.xml ├── issue2902.xml ├── issue2903.xml ├── issue2904.xml ├── issue2905.xml ├── issue2906.xml ├── issue2907.xml ├── issue2908.xml ├── issue2909.xml ├── issue2910.xml ├── issue2911.xml ├── issue2912.xml ├── issue2913.xml ├── issue2914.xml ├── issue2915.xml ├── issue2916.xml ├── issue2917.xml ├── issue2918.xml ├── issue2919.xml ├── issue2920.xml ├── issue2921.xml ├── issue2922.xml ├── issue2923.xml ├── issue2924.xml ├── issue2925.xml ├── issue2926.xml ├── issue2927.xml ├── issue2928.xml ├── issue2929.xml ├── issue2930.xml ├── issue2931.xml ├── issue2932.xml ├── issue2933.xml ├── issue2934.xml ├── issue2935.xml ├── issue2936.xml ├── issue2937.xml ├── issue2938.xml ├── issue2939.xml ├── issue2940.xml ├── issue2941.xml ├── issue2942.xml ├── issue2943.xml ├── issue2944.xml ├── issue2945.xml ├── issue2946.xml ├── issue2947.xml ├── issue2948.xml ├── issue2949.xml ├── issue2950.xml ├── issue2951.xml ├── issue2952.xml ├── issue2953.xml ├── issue2954.xml ├── issue2955.xml ├── issue2956.xml ├── issue2957.xml ├── issue2958.xml ├── issue2959.xml ├── issue2960.xml ├── issue2961.xml ├── issue2962.xml ├── issue2963.xml ├── issue2964.xml ├── issue2965.xml ├── issue2966.xml ├── issue2967.xml ├── issue2968.xml ├── issue2969.xml ├── issue2970.xml ├── issue2971.xml ├── issue2972.xml ├── issue2973.xml ├── issue2974.xml ├── issue2975.xml ├── issue2976.xml ├── issue2977.xml ├── issue2978.xml ├── issue2979.xml ├── issue2980.xml ├── issue2981.xml ├── issue2982.xml ├── issue2983.xml ├── issue2984.xml ├── issue2985.xml ├── issue2986.xml ├── issue2987.xml ├── issue2988.xml ├── issue2989.xml ├── issue2990.xml ├── issue2991.xml ├── issue2992.xml ├── issue2993.xml ├── issue2994.xml ├── issue2995.xml ├── issue2996.xml ├── issue2997.xml ├── issue2998.xml ├── issue2999.xml ├── issue3000.xml ├── issue3001.xml ├── issue3002.xml ├── issue3003.xml ├── issue3004.xml ├── issue3005.xml ├── issue3006.xml ├── issue3007.xml ├── issue3008.xml ├── issue3009.xml ├── issue3010.xml ├── issue3011.xml ├── issue3012.xml ├── issue3013.xml ├── issue3014.xml ├── issue3015.xml ├── issue3016.xml ├── issue3017.xml ├── issue3018.xml ├── issue3019.xml ├── issue3020.xml ├── issue3021.xml ├── issue3022.xml ├── issue3023.xml ├── issue3024.xml ├── issue3025.xml ├── issue3026.xml ├── issue3027.xml ├── issue3028.xml ├── issue3029.xml ├── issue3030.xml ├── issue3031.xml ├── issue3032.xml ├── issue3033.xml ├── issue3034.xml ├── issue3035.xml ├── issue3036.xml ├── issue3037.xml ├── issue3038.xml ├── issue3039.xml ├── issue3040.xml ├── issue3041.xml ├── issue3042.xml ├── issue3043.xml ├── issue3044.xml ├── issue3045.xml ├── issue3046.xml ├── issue3047.xml ├── issue3048.xml ├── issue3049.xml ├── issue3050.xml ├── issue3051.xml ├── issue3052.xml ├── issue3053.xml ├── issue3054.xml ├── issue3055.xml ├── issue3056.xml ├── issue3057.xml ├── issue3058.xml ├── issue3059.xml ├── issue3060.xml ├── issue3061.xml ├── issue3062.xml ├── issue3063.xml ├── issue3064.xml ├── issue3065.xml ├── issue3066.xml ├── issue3067.xml ├── issue3068.xml ├── issue3069.xml ├── issue3070.xml ├── issue3071.xml ├── issue3072.xml ├── issue3073.xml ├── issue3074.xml ├── issue3075.xml ├── issue3076.xml ├── issue3077.xml ├── issue3078.xml ├── issue3079.xml ├── issue3080.xml ├── issue3081.xml ├── issue3082.xml ├── issue3083.xml ├── issue3084.xml ├── issue3085.xml ├── issue3086.xml ├── issue3087.xml ├── issue3088.xml ├── issue3089.xml ├── issue3090.xml ├── issue3091.xml ├── issue3092.xml ├── issue3093.xml ├── issue3094.xml ├── issue3095.xml ├── issue3096.xml ├── issue3097.xml ├── issue3098.xml ├── issue3099.xml ├── issue3100.xml ├── issue3101.xml ├── issue3102.xml ├── issue3103.xml ├── issue3104.xml ├── issue3105.xml ├── issue3106.xml ├── issue3107.xml ├── issue3108.xml ├── issue3109.xml ├── issue3110.xml ├── issue3111.xml ├── issue3112.xml ├── issue3113.xml ├── issue3114.xml ├── issue3115.xml ├── issue3116.xml ├── issue3117.xml ├── issue3118.xml ├── issue3119.xml ├── issue3120.xml ├── issue3121.xml ├── issue3122.xml ├── issue3123.xml ├── issue3124.xml ├── issue3125.xml ├── issue3126.xml ├── issue3127.xml ├── issue3128.xml ├── issue3129.xml ├── issue3130.xml ├── issue3131.xml ├── issue3132.xml ├── issue3133.xml ├── issue3134.xml ├── issue3135.xml ├── issue3136.xml ├── issue3137.xml ├── issue3138.xml ├── issue3139.xml ├── issue3140.xml ├── issue3141.xml ├── issue3142.xml ├── issue3143.xml ├── issue3144.xml ├── issue3145.xml ├── issue3146.xml ├── issue3147.xml ├── issue3148.xml ├── issue3149.xml ├── issue3150.xml ├── issue3151.xml ├── issue3152.xml ├── issue3153.xml ├── issue3154.xml ├── issue3155.xml ├── issue3156.xml ├── issue3157.xml ├── issue3158.xml ├── issue3159.xml ├── issue3160.xml ├── issue3161.xml ├── issue3162.xml ├── issue3163.xml ├── issue3164.xml ├── issue3165.xml ├── issue3166.xml ├── issue3167.xml ├── issue3168.xml ├── issue3169.xml ├── issue3170.xml ├── issue3171.xml ├── issue3172.xml ├── issue3173.xml ├── issue3174.xml ├── issue3175.xml ├── issue3176.xml ├── issue3177.xml ├── issue3178.xml ├── issue3179.xml ├── issue3180.xml ├── issue3181.xml ├── issue3182.xml ├── issue3183.xml ├── issue3184.xml ├── issue3185.xml ├── issue3186.xml ├── issue3187.xml ├── issue3188.xml ├── issue3189.xml ├── issue3190.xml ├── issue3191.xml ├── issue3192.xml ├── issue3193.xml ├── issue3194.xml ├── issue3195.xml ├── issue3196.xml ├── issue3197.xml ├── issue3198.xml ├── issue3199.xml ├── issue3200.xml ├── issue3201.xml ├── issue3202.xml ├── issue3203.xml ├── issue3204.xml ├── issue3205.xml ├── issue3206.xml ├── issue3207.xml ├── issue3208.xml ├── issue3209.xml ├── issue3210.xml ├── issue3211.xml ├── issue3212.xml ├── issue3213.xml ├── issue3214.xml ├── issue3215.xml ├── issue3216.xml ├── issue3217.xml ├── issue3218.xml ├── issue3219.xml ├── issue3220.xml ├── issue3221.xml ├── issue3222.xml ├── issue3223.xml ├── issue3224.xml ├── issue3225.xml ├── issue3226.xml ├── issue3227.xml ├── issue3228.xml ├── issue3229.xml ├── issue3230.xml ├── issue3231.xml ├── issue3232.xml ├── issue3233.xml ├── issue3234.xml ├── issue3235.xml ├── issue3236.xml ├── issue3237.xml ├── issue3238.xml ├── issue3239.xml ├── issue3240.xml ├── issue3241.xml ├── issue3242.xml ├── issue3243.xml ├── issue3244.xml ├── issue3245.xml ├── issue3246.xml ├── issue3247.xml ├── issue3248.xml ├── issue3249.xml ├── issue3250.xml ├── issue3251.xml ├── issue3252.xml ├── issue3253.xml ├── issue3254.xml ├── issue3255.xml ├── issue3256.xml ├── issue3257.xml ├── issue3258.xml ├── issue3259.xml ├── issue3260.xml ├── issue3261.xml ├── issue3262.xml ├── issue3263.xml ├── issue3264.xml ├── issue3265.xml ├── issue3266.xml ├── issue3267.xml ├── issue3268.xml ├── issue3269.xml ├── issue3270.xml ├── issue3271.xml ├── issue3272.xml ├── issue3273.xml ├── issue3274.xml ├── issue3275.xml ├── issue3276.xml ├── issue3277.xml ├── issue3278.xml ├── issue3279.xml ├── issue3280.xml ├── issue3281.xml ├── issue3282.xml ├── issue3283.xml ├── issue3284.xml ├── issue3285.xml ├── issue3286.xml ├── issue3287.xml ├── issue3288.xml ├── issue3289.xml ├── issue3290.xml ├── issue3291.xml ├── issue3292.xml ├── issue3293.xml ├── issue3294.xml ├── issue3295.xml ├── issue3296.xml ├── issue3297.xml ├── issue3298.xml ├── issue3299.xml ├── issue3300.xml ├── issue3301.xml ├── issue3302.xml ├── issue3303.xml ├── issue3304.xml ├── issue3305.xml ├── issue3306.xml ├── issue3307.xml ├── issue3308.xml ├── issue3309.xml ├── issue3310.xml ├── issue3311.xml ├── issue3312.xml ├── issue3313.xml ├── issue3314.xml ├── issue3315.xml ├── issue3316.xml ├── issue3317.xml ├── issue3318.xml ├── issue3319.xml ├── issue3320.xml ├── issue3321.xml ├── issue3322.xml ├── issue3323.xml ├── issue3324.xml ├── issue3325.xml ├── issue3326.xml ├── issue3327.xml ├── issue3328.xml ├── issue3329.xml ├── issue3330.xml ├── issue3331.xml ├── issue3332.xml ├── issue3333.xml ├── issue3334.xml ├── issue3335.xml ├── issue3336.xml ├── issue3337.xml ├── issue3338.xml ├── issue3339.xml ├── issue3340.xml ├── issue3341.xml ├── issue3342.xml ├── issue3343.xml ├── issue3344.xml ├── issue3345.xml ├── issue3346.xml ├── issue3347.xml ├── issue3348.xml ├── issue3349.xml ├── issue3350.xml ├── issue3351.xml ├── issue3352.xml ├── issue3353.xml ├── issue3354.xml ├── issue3355.xml ├── issue3356.xml ├── issue3357.xml ├── issue3358.xml ├── issue3359.xml ├── issue3360.xml ├── issue3361.xml ├── issue3362.xml ├── issue3363.xml ├── issue3364.xml ├── issue3365.xml ├── issue3366.xml ├── issue3367.xml ├── issue3368.xml ├── issue3369.xml ├── issue3370.xml ├── issue3371.xml ├── issue3372.xml ├── issue3373.xml ├── issue3374.xml ├── issue3375.xml ├── issue3376.xml ├── issue3377.xml ├── issue3378.xml ├── issue3379.xml ├── issue3380.xml ├── issue3381.xml ├── issue3382.xml ├── issue3383.xml ├── issue3384.xml ├── issue3385.xml ├── issue3386.xml ├── issue3387.xml ├── issue3388.xml ├── issue3389.xml ├── issue3390.xml ├── issue3391.xml ├── issue3392.xml ├── issue3393.xml ├── issue3394.xml ├── issue3395.xml ├── issue3396.xml ├── issue3397.xml ├── issue3398.xml ├── issue3399.xml ├── issue3400.xml ├── issue3401.xml ├── issue3402.xml ├── issue3403.xml ├── issue3404.xml ├── issue3405.xml ├── issue3406.xml ├── issue3407.xml ├── issue3408.xml ├── issue3409.xml ├── issue3410.xml ├── issue3411.xml ├── issue3412.xml ├── issue3413.xml ├── issue3414.xml ├── issue3415.xml ├── issue3416.xml ├── issue3417.xml ├── issue3418.xml ├── issue3419.xml ├── issue3420.xml ├── issue3421.xml ├── issue3422.xml ├── issue3423.xml ├── issue3424.xml ├── issue3425.xml ├── issue3426.xml ├── issue3427.xml ├── issue3428.xml ├── issue3429.xml ├── issue3430.xml ├── issue3431.xml ├── issue3432.xml ├── issue3433.xml ├── issue3434.xml ├── issue3435.xml ├── issue3436.xml ├── issue3437.xml ├── issue3438.xml ├── issue3439.xml ├── issue3440.xml ├── issue3441.xml ├── issue3442.xml ├── issue3443.xml ├── issue3444.xml ├── issue3445.xml ├── issue3446.xml ├── issue3447.xml ├── issue3448.xml ├── issue3449.xml ├── issue3450.xml ├── issue3451.xml ├── issue3452.xml ├── issue3453.xml ├── issue3454.xml ├── issue3455.xml ├── issue3456.xml ├── issue3457.xml ├── issue3458.xml ├── issue3459.xml ├── issue3460.xml ├── issue3461.xml ├── issue3462.xml ├── issue3463.xml ├── issue3464.xml ├── issue3465.xml ├── issue3466.xml ├── issue3467.xml ├── issue3468.xml ├── issue3469.xml ├── issue3470.xml ├── issue3471.xml ├── issue3472.xml ├── issue3473.xml ├── issue3474.xml ├── issue3475.xml ├── issue3476.xml ├── issue3477.xml ├── issue3478.xml ├── issue3479.xml ├── issue3480.xml ├── issue3481.xml ├── issue3482.xml ├── issue3483.xml ├── issue3484.xml ├── issue3485.xml ├── issue3486.xml ├── issue3487.xml ├── issue3488.xml ├── issue3489.xml ├── issue3490.xml ├── issue3491.xml ├── issue3492.xml ├── issue3493.xml ├── issue3494.xml ├── issue3495.xml ├── issue3496.xml ├── issue3497.xml ├── issue3498.xml ├── issue3499.xml ├── issue3500.xml ├── issue3501.xml ├── issue3502.xml ├── issue3503.xml ├── issue3504.xml ├── issue3505.xml ├── issue3506.xml ├── issue3507.xml ├── issue3508.xml ├── issue3509.xml ├── issue3510.xml ├── issue3511.xml ├── issue3512.xml ├── issue3513.xml ├── issue3514.xml ├── issue3515.xml ├── issue3516.xml ├── issue3517.xml ├── issue3518.xml ├── issue3519.xml ├── issue3520.xml ├── issue3521.xml ├── issue3522.xml ├── issue3523.xml ├── issue3524.xml ├── issue3525.xml ├── issue3526.xml ├── issue3527.xml ├── issue3528.xml ├── issue3529.xml ├── issue3530.xml ├── issue3531.xml ├── issue3532.xml ├── issue3533.xml ├── issue3534.xml ├── issue3535.xml ├── issue3536.xml ├── issue3537.xml ├── issue3538.xml ├── issue3539.xml ├── issue3540.xml ├── issue3541.xml ├── issue3542.xml ├── issue3543.xml ├── issue3544.xml ├── issue3545.xml ├── issue3546.xml ├── issue3547.xml ├── issue3548.xml ├── issue3549.xml ├── issue3550.xml ├── issue3551.xml ├── issue3552.xml ├── issue3553.xml ├── issue3554.xml ├── issue3555.xml ├── issue3556.xml ├── issue3557.xml ├── issue3558.xml ├── issue3559.xml ├── issue3560.xml ├── issue3561.xml ├── issue3562.xml ├── issue3563.xml ├── issue3564.xml ├── issue3565.xml ├── issue3566.xml ├── issue3567.xml ├── issue3568.xml ├── issue3569.xml ├── issue3570.xml ├── issue3571.xml ├── issue3572.xml ├── issue3573.xml ├── issue3574.xml ├── issue3575.xml ├── issue3576.xml ├── issue3577.xml ├── issue3578.xml ├── issue3579.xml ├── issue3580.xml ├── issue3581.xml ├── issue3582.xml ├── issue3583.xml ├── issue3584.xml ├── issue3585.xml ├── issue3586.xml ├── issue3587.xml ├── issue3588.xml ├── issue3589.xml ├── issue3590.xml ├── issue3591.xml ├── issue3592.xml ├── issue3593.xml ├── issue3594.xml ├── issue3595.xml ├── issue3596.xml ├── issue3597.xml ├── issue3598.xml ├── issue3599.xml ├── issue3600.xml ├── issue3601.xml ├── issue3602.xml ├── issue3603.xml ├── issue3604.xml ├── issue3605.xml ├── issue3606.xml ├── issue3607.xml ├── issue3608.xml ├── issue3609.xml ├── issue3610.xml ├── issue3611.xml ├── issue3612.xml ├── issue3613.xml ├── issue3614.xml ├── issue3615.xml ├── issue3616.xml ├── issue3617.xml ├── issue3618.xml ├── issue3619.xml ├── issue3620.xml ├── issue3621.xml ├── issue3622.xml ├── issue3623.xml ├── issue3624.xml ├── issue3625.xml ├── issue3626.xml ├── issue3627.xml ├── issue3628.xml ├── issue3629.xml ├── issue3630.xml ├── issue3631.xml ├── issue3632.xml ├── issue3633.xml ├── issue3634.xml ├── issue3635.xml ├── issue3636.xml ├── issue3637.xml ├── issue3638.xml ├── issue3639.xml ├── issue3640.xml ├── issue3641.xml ├── issue3642.xml ├── issue3643.xml ├── issue3644.xml ├── issue3645.xml ├── issue3646.xml ├── issue3647.xml ├── issue3648.xml ├── issue3649.xml ├── issue3650.xml ├── issue3651.xml ├── issue3652.xml ├── issue3653.xml ├── issue3654.xml ├── issue3655.xml ├── issue3656.xml ├── issue3657.xml ├── issue3658.xml ├── issue3659.xml ├── issue3660.xml ├── issue3661.xml ├── issue3662.xml ├── issue3663.xml ├── issue3664.xml ├── issue3665.xml ├── issue3666.xml ├── issue3667.xml ├── issue3668.xml ├── issue3669.xml ├── issue3670.xml ├── issue3671.xml ├── issue3672.xml ├── issue3673.xml ├── issue3674.xml ├── issue3675.xml ├── issue3676.xml ├── issue3677.xml ├── issue3678.xml ├── issue3679.xml ├── issue3680.xml ├── issue3681.xml ├── issue3682.xml ├── issue3683.xml ├── issue3684.xml ├── issue3685.xml ├── issue3686.xml ├── issue3687.xml ├── issue3688.xml ├── issue3689.xml ├── issue3690.xml ├── issue3691.xml ├── issue3692.xml ├── issue3693.xml ├── issue3694.xml ├── issue3695.xml ├── issue3696.xml ├── issue3697.xml ├── issue3698.xml ├── issue3699.xml ├── issue3700.xml ├── issue3701.xml ├── issue3702.xml ├── issue3703.xml ├── issue3704.xml ├── issue3705.xml ├── issue3706.xml ├── issue3707.xml ├── issue3708.xml ├── issue3709.xml ├── issue3710.xml ├── issue3711.xml ├── issue3712.xml ├── issue3713.xml ├── issue3714.xml ├── issue3715.xml ├── issue3716.xml ├── issue3717.xml ├── issue3718.xml ├── issue3719.xml ├── issue3720.xml ├── issue3721.xml ├── issue3722.xml ├── issue3723.xml ├── issue3724.xml ├── issue3725.xml ├── issue3726.xml ├── issue3727.xml ├── issue3728.xml ├── issue3729.xml ├── issue3730.xml ├── issue3731.xml ├── issue3732.xml ├── issue3733.xml ├── issue3734.xml ├── issue3735.xml ├── issue3736.xml ├── issue3737.xml ├── issue3738.xml ├── issue3739.xml ├── issue3740.xml ├── issue3741.xml ├── issue3742.xml ├── issue3743.xml ├── issue3744.xml ├── issue3745.xml ├── issue3746.xml ├── issue3747.xml ├── issue3748.xml ├── issue3749.xml ├── issue3750.xml ├── issue3751.xml ├── issue3752.xml ├── issue3753.xml ├── issue3754.xml ├── issue3755.xml ├── issue3756.xml ├── issue3757.xml ├── issue3758.xml ├── issue3759.xml ├── issue3760.xml ├── issue3761.xml ├── issue3762.xml ├── issue3763.xml ├── issue3764.xml ├── issue3765.xml ├── issue3766.xml ├── issue3767.xml ├── issue3768.xml ├── issue3769.xml ├── issue3770.xml ├── issue3771.xml ├── issue3772.xml ├── issue3773.xml ├── issue3774.xml ├── issue3775.xml ├── issue3776.xml ├── issue3777.xml ├── issue3778.xml ├── issue3779.xml ├── issue3780.xml ├── issue3781.xml ├── issue3782.xml ├── issue3783.xml ├── issue3784.xml ├── issue3785.xml ├── issue3786.xml ├── issue3787.xml ├── issue3788.xml ├── issue3789.xml ├── issue3790.xml ├── issue3791.xml ├── issue3792.xml ├── issue3793.xml ├── issue3794.xml ├── issue3795.xml ├── issue3796.xml ├── issue3797.xml ├── issue3798.xml ├── issue3799.xml ├── issue3800.xml ├── issue3801.xml ├── issue3802.xml ├── issue3803.xml ├── issue3804.xml ├── issue3805.xml ├── issue3806.xml ├── issue3807.xml ├── issue3808.xml ├── issue3809.xml ├── issue3810.xml ├── issue3811.xml ├── issue3812.xml ├── issue3813.xml ├── issue3814.xml ├── issue3815.xml ├── issue3816.xml ├── issue3817.xml ├── issue3818.xml ├── issue3819.xml ├── issue3820.xml ├── issue3821.xml ├── issue3822.xml ├── issue3823.xml ├── issue3824.xml ├── issue3825.xml ├── issue3826.xml ├── issue3827.xml ├── issue3828.xml ├── issue3829.xml ├── issue3830.xml ├── issue3831.xml ├── issue3832.xml ├── issue3833.xml ├── issue3834.xml ├── issue3835.xml ├── issue3836.xml ├── issue3837.xml ├── issue3838.xml ├── issue3839.xml ├── issue3840.xml ├── issue3841.xml ├── issue3842.xml ├── issue3843.xml ├── issue3844.xml ├── issue3845.xml ├── issue3846.xml ├── issue3847.xml ├── issue3848.xml ├── issue3849.xml ├── issue3850.xml ├── issue3851.xml ├── issue3852.xml ├── issue3853.xml ├── issue3854.xml ├── issue3855.xml ├── issue3856.xml ├── issue3857.xml ├── issue3858.xml ├── issue3859.xml ├── issue3860.xml ├── issue3861.xml ├── issue3862.xml ├── issue3863.xml ├── issue3864.xml ├── issue3865.xml ├── issue3866.xml ├── issue3867.xml ├── issue3868.xml ├── issue3869.xml ├── issue3870.xml ├── issue3871.xml ├── issue3872.xml ├── issue3873.xml ├── issue3874.xml ├── issue3875.xml ├── issue3876.xml ├── issue3877.xml ├── issue3878.xml ├── issue3879.xml ├── issue3880.xml ├── issue3881.xml ├── issue3882.xml ├── issue3883.xml ├── issue3884.xml ├── issue3885.xml ├── issue3886.xml ├── issue3887.xml ├── issue3888.xml ├── issue3889.xml ├── issue3890.xml ├── issue3891.xml ├── issue3892.xml ├── issue3893.xml ├── issue3894.xml ├── issue3895.xml ├── issue3896.xml ├── issue3897.xml ├── issue3898.xml ├── issue3899.xml ├── issue3900.xml ├── issue3901.xml ├── issue3902.xml ├── issue3903.xml ├── issue3904.xml ├── issue3905.xml ├── issue3906.xml ├── issue3907.xml ├── issue3908.xml ├── issue3909.xml ├── issue3910.xml ├── issue3911.xml ├── issue3912.xml ├── issue3913.xml ├── issue3914.xml ├── issue3915.xml ├── issue3916.xml ├── issue3917.xml ├── issue3918.xml ├── issue3919.xml ├── issue3920.xml ├── issue3921.xml ├── issue3922.xml ├── issue3923.xml ├── issue3924.xml ├── issue3925.xml ├── issue3926.xml ├── issue3927.xml ├── issue3928.xml ├── issue3929.xml ├── issue3930.xml ├── issue3931.xml ├── issue3932.xml ├── issue3933.xml ├── issue3934.xml ├── issue3935.xml ├── issue3936.xml ├── issue3937.xml ├── issue3938.xml ├── issue3939.xml ├── issue3940.xml ├── issue3941.xml ├── issue3942.xml ├── issue3943.xml ├── issue3944.xml ├── issue3945.xml ├── issue3946.xml ├── issue3947.xml ├── issue3948.xml ├── issue3949.xml ├── issue3950.xml ├── issue3951.xml ├── issue3952.xml ├── issue3953.xml ├── issue3954.xml ├── issue3955.xml ├── issue3956.xml ├── issue3957.xml ├── issue3958.xml ├── issue3959.xml ├── issue3960.xml ├── issue3961.xml ├── issue3962.xml ├── issue3963.xml ├── issue3964.xml ├── issue3965.xml ├── issue3966.xml ├── issue3967.xml ├── issue3968.xml ├── issue3969.xml ├── issue3970.xml ├── issue3971.xml ├── issue3972.xml ├── issue3973.xml ├── issue3974.xml ├── issue3975.xml ├── issue3976.xml ├── issue3977.xml ├── issue3978.xml ├── issue3979.xml ├── issue3980.xml ├── issue3981.xml ├── issue3982.xml ├── issue3983.xml ├── issue3984.xml ├── issue3985.xml ├── issue3986.xml ├── issue3987.xml ├── issue3988.xml ├── issue3989.xml ├── issue3990.xml ├── issue3991.xml ├── issue3992.xml ├── issue3993.xml ├── issue3994.xml ├── issue3995.xml ├── issue3996.xml ├── issue3997.xml ├── issue3998.xml ├── issue3999.xml ├── issue4000.xml ├── issue4001.xml ├── issue4002.xml ├── issue4003.xml ├── issue4004.xml ├── issue4005.xml ├── issue4006.xml ├── issue4007.xml ├── issue4008.xml ├── issue4009.xml ├── issue4010.xml ├── issue4011.xml ├── issue4012.xml ├── issue4013.xml ├── issue4014.xml ├── issue4015.xml ├── issue4016.xml ├── issue4017.xml ├── issue4018.xml ├── issue4019.xml ├── issue4020.xml ├── issue4021.xml ├── issue4022.xml ├── issue4023.xml ├── issue4024.xml ├── issue4025.xml ├── issue4026.xml ├── issue4027.xml ├── issue4028.xml ├── issue4029.xml ├── issue4030.xml ├── issue4031.xml ├── issue4032.xml ├── issue4033.xml ├── issue4034.xml ├── issue4035.xml ├── issue4036.xml ├── issue4037.xml ├── issue4038.xml ├── issue4039.xml ├── issue4040.xml ├── issue4041.xml ├── issue4042.xml ├── issue4043.xml ├── issue4044.xml ├── issue4045.xml ├── issue4046.xml ├── issue4047.xml ├── issue4048.xml ├── issue4049.xml ├── issue4050.xml ├── issue4051.xml ├── issue4052.xml ├── issue4053.xml ├── issue4054.xml ├── issue4055.xml ├── issue4056.xml ├── issue4057.xml ├── issue4058.xml ├── issue4059.xml ├── issue4060.xml ├── issue4061.xml ├── issue4062.xml ├── issue4063.xml ├── issue4064.xml ├── issue4065.xml ├── issue4066.xml ├── issue4067.xml ├── issue4068.xml ├── issue4069.xml ├── issue4070.xml ├── issue4071.xml ├── issue4072.xml ├── issue4073.xml ├── issue4074.xml ├── issue4075.xml ├── issue4076.xml ├── issue4077.xml ├── issue4078.xml ├── issue4079.xml ├── issue4080.xml ├── issue4081.xml ├── issue4082.xml ├── issue4083.xml ├── issue4084.xml ├── issue4085.xml ├── issue4086.xml ├── issue4087.xml ├── issue4088.xml ├── issue4089.xml ├── issue4090.xml ├── issue4091.xml ├── issue4092.xml ├── issue4093.xml ├── issue4094.xml ├── issue4095.xml ├── issue4096.xml ├── issue4097.xml ├── issue4098.xml ├── issue4099.xml ├── issue4100.xml ├── issue4101.xml ├── issue4102.xml ├── issue4103.xml ├── issue4104.xml ├── issue4105.xml ├── issue4106.xml ├── issue4107.xml ├── issue4108.xml ├── issue4109.xml ├── issue4110.xml ├── issue4111.xml ├── issue4112.xml ├── issue4113.xml ├── issue4114.xml ├── issue4115.xml ├── issue4116.xml ├── issue4117.xml ├── issue4118.xml ├── issue4119.xml ├── issue4120.xml ├── issue4121.xml ├── issue4122.xml ├── issue4123.xml ├── issue4124.xml ├── issue4125.xml ├── issue4126.xml ├── issue4127.xml ├── issue4128.xml ├── issue4129.xml ├── issue4130.xml ├── issue4131.xml ├── issue4132.xml ├── issue4133.xml ├── issue4134.xml ├── issue4135.xml ├── issue4136.xml ├── issue4137.xml ├── issue4138.xml ├── issue4139.xml ├── issue4140.xml ├── issue4141.xml ├── issue4142.xml ├── issue4143.xml ├── issue4144.xml ├── issue4145.xml ├── issue4146.xml ├── issue4147.xml ├── issue4148.xml ├── issue4149.xml ├── issue4150.xml ├── issue4151.xml ├── issue4152.xml ├── issue4153.xml ├── issue4154.xml ├── issue4155.xml ├── issue4156.xml ├── issue4157.xml ├── issue4158.xml ├── issue4159.xml ├── issue4160.xml ├── issue4161.xml ├── issue4162.xml ├── issue4163.xml ├── issue4164.xml ├── issue4165.xml ├── issue4166.xml ├── issue4167.xml ├── issue4168.xml ├── issue4169.xml ├── issue4170.xml ├── issue4171.xml ├── issue4172.xml ├── issue4173.xml ├── issue4174.xml ├── issue4175.xml ├── issue4176.xml ├── issue4177.xml ├── issue4178.xml ├── issue4179.xml ├── issue4180.xml ├── issue4181.xml ├── issue4182.xml ├── issue4183.xml ├── issue4184.xml ├── issue4185.xml ├── issue4186.xml ├── issue4187.xml ├── issue4188.xml ├── issue4189.xml ├── issue4190.xml ├── issue4191.xml ├── issue4192.xml ├── issue4193.xml ├── issue4194.xml ├── issue4195.xml ├── issue4196.xml ├── issue4197.xml ├── issue4198.xml ├── issue4199.xml ├── issue4200.xml ├── issue4201.xml ├── issue4202.xml ├── issue4203.xml ├── issue4204.xml ├── issue4205.xml ├── issue4206.xml ├── issue4207.xml ├── issue4208.xml ├── issue4209.xml ├── issue4210.xml ├── issue4211.xml ├── issue4212.xml ├── issue4213.xml ├── issue4214.xml ├── issue4215.xml ├── issue4216.xml ├── issue4217.xml ├── issue4218.xml ├── issue4219.xml ├── issue4220.xml ├── issue4221.xml ├── issue4222.xml ├── issue4223.xml ├── issue4224.xml ├── issue4225.xml ├── issue4226.xml ├── issue4227.xml ├── issue4228.xml ├── issue4229.xml ├── issue4230.xml ├── issue4231.xml ├── issue4232.xml ├── issue4233.xml ├── issue4234.xml ├── issue4235.xml ├── issue4236.xml ├── issue4237.xml ├── issue4238.xml ├── issue4239.xml ├── issue4240.xml ├── issue4241.xml ├── issue4242.xml ├── issue4243.xml ├── issue4244.xml ├── issue4245.xml ├── issue4246.xml ├── issue4247.xml ├── issue4248.xml ├── issue4249.xml ├── issue4250.xml ├── issue4251.xml ├── issue4252.xml ├── issue4253.xml ├── issue4254.xml ├── issue4255.xml ├── issue4256.xml ├── issue4257.xml ├── issue4258.xml ├── issue4259.xml ├── issue4260.xml ├── issue4261.xml ├── issue4262.xml ├── issue4263.xml ├── issue4264.xml ├── issue4265.xml ├── issue4266.xml ├── issue4267.xml ├── issue4268.xml ├── issue4269.xml ├── issue4270.xml ├── issue4271.xml ├── issue4272.xml ├── issue4273.xml ├── issue4274.xml ├── issue4275.xml ├── issue4276.xml ├── issue4277.xml ├── issue4278.xml ├── issue4279.xml ├── issue4280.xml ├── issue4281.xml ├── issue4282.xml ├── issue4283.xml ├── issue4284.xml ├── issue4285.xml ├── issue4286.xml ├── issue4287.xml ├── issue4288.xml ├── issue4289.xml ├── issue4290.xml ├── issue4291.xml ├── issue4292.xml ├── issue4293.xml ├── issue4294.xml ├── issue4295.xml ├── issue4296.xml ├── lwg-issue.dtd ├── lwg-issues.xml └── lwg-template.xml /.gitignore: -------------------------------------------------------------------------------- 1 | /bin/lists.exe 2 | /bin/lists 3 | /bin/section_data.exe 4 | /bin/section_data 5 | /bin/toc_diff.exe 6 | /bin/toc_diff 7 | /bin/build_pgms_with_env.bat 8 | /bin/annex-f* 9 | /bin/section.data 10 | /bin/index 11 | /bin/list_issues.exe 12 | /bin/list_issues 13 | /bin/set_status.exe 14 | /bin/set_status 15 | /build 16 | /out 17 | /src/*.[do] 18 | /mailing 19 | /.vs 20 | /.vscode 21 | .DS_Store 22 | R*-mailing.zip 23 | /meta-data/annex-f 24 | /meta-data/networking-annex-f 25 | /meta-data/dates 26 | /meta-data/index.json 27 | -------------------------------------------------------------------------------- /README: -------------------------------------------------------------------------------- 1 | https://github.com/cplusplus/LWG is the repository for the C++ Standards Committee's 2 | Library Working Group issues lists files. 3 | 4 | For the most recent draft of the lists generated from these files, see 5 | https://cplusplus.github.io/LWG/lwg-active.html 6 | 7 | For the official (but less up-to-date) versions of these lists, see 8 | https://www.open-std.org/jtc1/sc22/wg21/ 9 | 10 | To submit a new issue, please read 11 | https://cplusplus.github.io/LWG/lwg-active.html#submit_issue 12 | 13 | For editorial mistakes and inconsistencies in the draft standard, see 14 | https://github.com/cplusplus/draft/wiki 15 | 16 | -------------------------------------------------------------------------------- /bin/build_lists.bat: -------------------------------------------------------------------------------- 1 | call git pull 2 | bin\build_lists_only 3 | -------------------------------------------------------------------------------- /bin/build_lists.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | git pull 3 | bin/build_lists_only.sh 4 | -------------------------------------------------------------------------------- /bin/build_lists_only.bat: -------------------------------------------------------------------------------- 1 | @echo off 2 | bin\lists 3 | if errorlevel 1 goto error 4 | mailing\lwg-active.html 5 | goto done 6 | 7 | :error 8 | echo *********************************** 9 | echo ********** build failure ********** 10 | echo *********************************** 11 | 12 | :done 13 | 14 | -------------------------------------------------------------------------------- /bin/build_lists_only.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | bin/lists && test -f mailing/lwg-active.html && exit 3 | echo "***********************************" 4 | echo "********** build failure **********" 5 | echo "***********************************" 6 | exit 1 7 | -------------------------------------------------------------------------------- /bin/build_pgms.bat: -------------------------------------------------------------------------------- 1 | echo "Use -m32 switch to force 32-bit build" 2 | g++ %* -std=c++17 -DNDEBUG -O2 -o bin/lists.exe src/date.cpp src/issues.cpp src/status.cpp src/sections.cpp src/mailing_info.cpp src/report_generator.cpp src/metadata.cpp src/lists.cpp 3 | g++ %* -std=c++17 -o bin/section_data.exe src/section_data.cpp 4 | g++ %* -std=c++17 -o bin/toc_diff.exe src/toc_diff.cpp 5 | g++ %* -std=c++17 -DNDEBUG -O2 -o bin/list_issues.exe src/date.cpp src/issues.cpp src/status.cpp src/sections.cpp src/metadata.cpp src/list_issues.cpp 6 | g++ %* -std=c++17 -DNDEBUG -O2 -o bin/set_status.exe src/set_status.cpp src/status.cpp 7 | 8 | -------------------------------------------------------------------------------- /bin/build_pgms.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | make -C $(dirname $0)/.. clean pgms 3 | -------------------------------------------------------------------------------- /bin/build_section_data.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | grep -v "^[A-Z]" bin/index 3 | bin/section_data bin/section.data 4 | 5 | if [ -e bin/networking-annex-f ]; then 6 | grep -v "^[A-Z]" bin/networking-index 7 | bin/section_data networking.ts bin/networking-section.data 8 | cat bin/networking-section.data >> bin/section.data 9 | else 10 | cat meta-data/networking-section.data >> bin/section.data 11 | fi 12 | cat meta-data/tr1_section.data >>bin/section.data 13 | cat meta-data/filesystem-section.data >>bin/section.data 14 | cat meta-data/lfts-old-section.data meta-data/lfts-v3-section.data >>bin/section.data 15 | ls -l bin/section.data 16 | -------------------------------------------------------------------------------- /bin/check-html-diffs.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | old=$(mktemp -d ./mailing.old.XXXXXX) 3 | new=$(mktemp -d ./mailing.new.XXXXXX) 4 | echo Building lists at HEAD 5 | make clean 6 | make lists -j4 7 | sed -i 's/Revised ....-..-.. at ..:..:.. UTC/Revised .../' mailing/*.html 8 | mv mailing $new 9 | git checkout ${1-origin/master} -- src 10 | echo Building lists with code from `git rev-parse origin/master` 11 | make clean 12 | make lists -j4 13 | git checkout HEAD -- src 14 | sed -i 's/Revised ....-..-.. at ..:..:.. UTC/Revised .../' mailing/*.html 15 | mv mailing $old 16 | diff -u -r --color=${2:-auto} $old $new || exit 17 | rm -r $old $new 18 | echo No changes to HTML files 19 | -------------------------------------------------------------------------------- /bin/lint.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | find xml -name 'issue*.xml' -print0 \ 3 | | xargs -0 -P $(getconf _NPROCESSORS_ONLN) -n 128 \ 4 | xmllint --noout --nowarning --dtdvalid xml/lwg-issue.dtd 5 | -------------------------------------------------------------------------------- /bin/make_dates.py: -------------------------------------------------------------------------------- 1 | #!/usr/bin/python 2 | 3 | # usage: git whatchanged --no-show-signature --pretty=%ct | python bin/make_dates.py > dates 4 | 5 | import sys 6 | import re 7 | 8 | # The input looks like 9 | # 1728481670 10 | # 11 | # :100644 100644 02412851ac 9f5998ba82 M xml/issue4159.xml 12 | # :100644 100644 fa2274aa17 74485b30c1 M xml/issue4162.xml 13 | # :100644 100644 8023699cb9 d007f71c08 M xml/issue4164.xml 14 | 15 | mtimes = {} 16 | current_mtime = '' 17 | for l in sys.stdin.readlines(): 18 | l = l.rstrip() 19 | if not l: 20 | # blank line 21 | continue 22 | 23 | # timestamp 24 | if l[0] != ':': 25 | current_mtime = l 26 | continue 27 | 28 | # last piece of line is the file name 29 | file = l.split()[-1] 30 | m = re.match('xml/issue(\\d+).xml', file) 31 | 32 | if m: 33 | num = int(m[1]) 34 | if num not in mtimes: 35 | mtimes[num] = current_mtime 36 | 37 | for (num, time) in sorted(list(mtimes.items())): 38 | print(f'{num:04} {time}') 39 | -------------------------------------------------------------------------------- /bin/make_paper_titles.py: -------------------------------------------------------------------------------- 1 | #!/usr/bin/python 2 | 3 | import json 4 | import sys 5 | import re 6 | 7 | latest_rev = {} 8 | 9 | with open(sys.argv[1]) as f: 10 | docs = json.load(f) 11 | for num,data in docs.items(): 12 | m = re.fullmatch(r'(P\d\d\d\d)R(\d+)|N\d\d\d\d', num) 13 | if m: 14 | print("{} {}".format(num, data['title'])) 15 | if num.startswith('P'): 16 | pnum = m[1] 17 | rev = int(m[2]) 18 | if rev > latest_rev.get(pnum, -1): 19 | latest_rev[pnum] = rev 20 | for pnum, rev in latest_rev.items(): 21 | pnumrev = "{}R{}".format(pnum, rev) 22 | print("{} {}".format(pnum, docs[pnumrev]['title'])) 23 | -------------------------------------------------------------------------------- /bin/sweep_voting_to_wp.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | # Sweep all issues from Voting -> WP 4 | 5 | if [ -z "$1" ] 6 | then 7 | echo "Usage: $0 ' YYYY-MM-DD'" >&2 8 | exit 1 9 | fi 10 | 11 | today=$(date +%F) 12 | meeting=$1 13 | date=$2 14 | 15 | # We could use awk -F'"' '/status="voting"/ { print $2}' xml/issue*.xml here, 16 | # but the wildcard matches thousands of files, so let git grep loop over them. 17 | git grep 'status="Voting"' xml | awk -F'"' '{print $2}' | while read inum 18 | do 19 | bin/set_status $inum WP 20 | sed -i "s/^$today /$meeting $date; /" xml/issue$inum.xml 21 | done 22 | -------------------------------------------------------------------------------- /bin/update_status.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | while read issue_number 3 | do 4 | bin/set_status $issue_number "$@" 5 | 6 | # To add a comment use the following (changing the date and text!) 7 | # sed -i '/<\/discussion/i\ 8 | #Tokyo 2024-03-23; Status changed: Voting → WP. 9 | #' xml/issue$issue_number.xml 10 | 11 | done 12 | -------------------------------------------------------------------------------- /meta-data/fund-index.bat: -------------------------------------------------------------------------------- 1 | @echo off 2 | if %1$==$ goto error 3 | if %2$==$ goto error 4 | grep "
" %1 | sed -r --file=fund-index.sed >%2 5 | echo Complete. See %2 6 | goto ok 7 | 8 | :error 9 | echo Invoke: fund_index html-input-file text-output-file 10 | 11 | :ok 12 | -------------------------------------------------------------------------------- /meta-data/fund-index.sed: -------------------------------------------------------------------------------- 1 | s/[ ]*
([0-9.]*)[^[]*\[([^]]*).*/fund.ts.v2 \1 [\2]/g 2 | s/([^<]*)<[^>]*>(.*)/\1\2/g 3 | s/([^<]*)<[^>]*>(.*)/\1\2/g 4 | -------------------------------------------------------------------------------- /meta-data/h-style-index.bat: -------------------------------------------------------------------------------- 1 | @echo off 2 | rem Prerequisite: POSIX grep and sed, such as from Cygwin 3 | if %1$==$ goto error 4 | if %2$==$ goto error 5 | if %3$==$ goto error 6 | grep "%3 7 | echo Complete. See %3 8 | echo TODO: Handle headings split across two lines. Filesystem TS needs that. 9 | goto ok 10 | 11 | :error 12 | echo Invoke: h-style-index section-prefix html-input-file text-output-file 13 | echo Example: h-style-index filesys.ts n4099.html temp.txt 14 | 15 | :ok 16 | -------------------------------------------------------------------------------- /meta-data/h-style-index.sed: -------------------------------------------------------------------------------- 1 | # Extract n.n... [xx.xxxx...] from HTML headers (e.g. "

1.2.3 Title [my.title]

"). 2 | # See h-style-index.bat for invokation. 3 | # TODO: Splice lines together first if headers extend across several lines 4 | s/[^0-9]*([0-9.]*)[^[]*\[([^]]*).*/section-prefix \1 [\2]/g 5 | s/([^<]*)<[^>]*>(.*)/\1\2/g 6 | s/([^<]*)<[^>]*>(.*)/\1\2/g 7 | -------------------------------------------------------------------------------- /src/html_utils.h: -------------------------------------------------------------------------------- 1 | #include 2 | #include 3 | 4 | namespace lwg 5 | { 6 | // Replace reserved characters with entities, for use as an attribute value. 7 | // Use for attributes like title="..." and content="...". 8 | inline std::string replace_reserved_char(std::string text, char c, std::string_view repl) { 9 | for (auto p = text.find(c); p != text.npos; p = text.find(c, p+repl.size())) 10 | text.replace(p, 1, repl); 11 | return text; 12 | } 13 | 14 | // Remove XML elements from the argument to just get the text nodes. 15 | // Used to generate plain text versions of elements like . 16 | inline std::string strip_xml_elements(std::string xml) { 17 | for (auto p = xml.find('<'); p != xml.npos; p = xml.find('<', p)) 18 | xml.erase(p, xml.find('>', p) + 1 - p); 19 | return xml; 20 | } 21 | 22 | struct issue; 23 | 24 | // Create an <a> element linking to an issue 25 | auto make_html_anchor(issue const & iss) -> std::string; 26 | 27 | } 28 | -------------------------------------------------------------------------------- /src/metadata.h: -------------------------------------------------------------------------------- 1 | #ifndef INCLUDE_LWG_METADATA_H 2 | #define INCLUDE_LWG_METADATA_H 3 | #include "sections.h" 4 | #include <map> 5 | #include <unordered_map> 6 | #include <ctime> 7 | #include <filesystem> 8 | 9 | namespace lwg { 10 | 11 | // Various things read from meta-data/ 12 | struct metadata { 13 | section_map section_db; 14 | std::map<int, std::time_t> git_commit_times; 15 | std::unordered_map<std::string, std::string> paper_titles; 16 | 17 | static metadata read_from_path(std::filesystem::path const& path); 18 | }; 19 | 20 | } 21 | #endif 22 | -------------------------------------------------------------------------------- /xml/issue0002.xml: -------------------------------------------------------------------------------- 1 | <?xml version='1.0' encoding='utf-8' standalone='no'?> 2 | <!DOCTYPE issue SYSTEM "lwg-issue.dtd"> 3 | 4 | <issue num="2" status="NAD"> 5 | <title>Auto_ptr conversions effects incorrect 6 |
7 | Nathan Myers 8 | 4 Dec 1997 9 | 10 | 11 |

Paragraph 1 in "Effects", says "Calls 12 | p->release()" where it clearly must be "Calls 13 | p.release()". (As it is, it seems to require using 14 | auto_ptr<>::operator-> to refer to X::release, assuming that 15 | exists.)

16 | 17 | 18 | 19 |

Change paragraph 1 Effects from 20 | "Calls p->release()" to "Calls p.release()".

21 | 22 | 23 | 24 |

Not a defect: the proposed change is already found in the standard. 25 | [Originally classified as a defect, later reclassified.]

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0008.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Locale::global lacks guarantee 6 |
7 | Matt Austern 8 | 24 Dec 1997 9 | 10 | 11 |

It appears there's an important guarantee missing from clause 12 | 22. We're told that invoking locale::global(L) sets the C locale if L 13 | has a name. However, we're not told whether or not invoking 14 | setlocale(s) sets the global C++ locale.

15 | 16 |

The intent, I think, is that it should not, but I can't find any 17 | such words anywhere.

18 | 19 | 20 | 21 |

Add a sentence at the end of , 22 | paragraph 2: 

23 | 24 |
25 |

No library function other than locale::global() shall affect 26 | the value returned by locale().

27 | 28 |
29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0010.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Codecvt<>::do unclear 6 |
7 | Matt Austern 8 | 14 Jan 1998 9 | 10 | 11 |

Section 22.2.1.5.2 says that codecvt<>::do_in and do_out 12 | should return the value noconv if "no conversion was 13 | needed". However, I don't see anything anywhere that defines what 14 | it means for a conversion to be needed or not needed. I can think of 15 | several circumstances where one might plausibly think that a 16 | conversion is not "needed", but I don't know which one is 17 | intended here.

18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue0013.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Eos refuses to die 6 |
7 | William M. Miller 8 | 3 Mar 1998 9 | 10 | 11 |

In 27.6.1.2.3, there is a reference to "eos", which is 12 | the only one in the whole draft (at least using Acrobat search), so 13 | it's undefined.

14 | 15 | 16 | 17 |

In , replace "eos" with 18 | "charT()"

19 | 20 | 21 | 22 | -------------------------------------------------------------------------------- /xml/issue0015.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Locale::name requirement inconsistent 6 |
7 | Nathan Myers 8 | 6 Aug 1998 9 | 10 | 11 |

locale::name() is described as returning a string that can be passed to a locale 12 | constructor, but there is no matching constructor.

13 | 14 | 15 | 16 |

In , paragraph 5, replace 17 | "locale(name())" with 18 | "locale(name().c_str())". 19 |

20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue0016.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Bad ctype_byname<char> decl 6 |
7 | Nathan Myers 8 | 6 Aug 1998 9 | 10 | 11 |

The new virtual members ctype_byname<char>::do_widen and do_narrow did not get 12 | edited in properly. Instead, the member do_widen appears four times, with wrong argument 13 | lists.

14 | 15 | 16 | 17 |

The correct declarations for the overloaded members 18 | do_narrow and do_widen should be copied 19 | from .

20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue0018.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Get(...bool&) omitted 6 |
7 | Nathan Myers 8 | 6 Aug 1998 9 | 10 | 11 |

In the list of num_get<> non-virtual members on page 22-23, the member 12 | that parses bool values was omitted from the list of definitions of non-virtual 13 | members, though it is listed in the class definition and the corresponding 14 | virtual is listed everywhere appropriate.

15 | 16 | 17 | 18 |

Add at the beginning of 19 | another get member for bool&, copied from the entry in 20 | .

21 | 22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0020.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Thousands_sep returns wrong type 6 |
7 | Nathan Myers 8 | 6 Aug 1998 9 | 10 | 11 |

The synopsis for numpunct<>::do_thousands_sep, and the 12 | definition of numpunct<>::thousands_sep which calls it, specify 13 | that it returns a value of type char_type. Here it is erroneously 14 | described as returning a "string_type".

15 | 16 | 17 | 18 |

In , above paragraph 2, change 19 | "string_type" to "char_type".

20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue0021.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | 8 | Codecvt_byname<> instantiations 9 |
10 | Nathan Myers 11 | 6 Aug 1998 12 | 13 | 14 |

In the second table in the section, captioned "Required 15 | instantiations", the instantiations for codecvt_byname<> 16 | have been omitted. These are necessary to allow users to construct a 17 | locale by name from facets.

18 | 19 | 20 | 21 |

Add in to the table captioned 22 | "Required instantiations", in the category "ctype" 23 | the lines

24 | 25 |
26 | 
codecvt_byname<char,char,mbstate_t>,
27 | codecvt_byname<wchar_t,char,mbstate_t>
28 |
29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0024.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | "do_convert" doesn't exist 8 |
9 | Nathan Myers 10 | 6 Aug 1998 11 | 12 | 13 |

The description of codecvt<>::do_out and do_in mentions a 14 | symbol "do_convert" which is not defined in the 15 | standard. This is a leftover from an edit, and should be "do_in 16 | and do_out".

17 | 18 | 19 | 20 |

In , paragraph 3, change 21 | "do_convert" to "do_in or do_out". Also, in , change "do_convert()" to "do_in 22 | or do_out".

23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue0030.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Wrong header for LC_* 8 |
9 | Nathan Myers 10 | 6 Aug 1998 11 | 12 | 13 |

Paragraph 2 implies that the C macros LC_CTYPE etc. are defined in <cctype>, 14 | where they are in fact defined elsewhere to appear in <clocale>.

15 | 16 | 17 | 18 |

In , paragraph 2, change 19 | "<cctype>" to read "<clocale>".

20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue0034.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | True/falsename() not in ctype<> 8 |
9 | Nathan Myers 10 | 6 Aug 1998 11 | 12 | 13 |

In paragraph 19, Effects:, members truename() and falsename are used from facet 14 | ctype<charT>, but it has no such members. Note that this is also a problem in 15 | 22.2.2.1.2, addressed in (4).

16 | 17 | 18 | 19 |

In , paragraph 19, in the Effects: 20 | clause for member put(...., bool), replace the initialization of the 21 | string_type value s as follows:

22 | 23 |
24 | 
const numpunct& np = use_facet<numpunct<charT> >(loc);
25 | string_type s = val ? np.truename() : np.falsename();
26 |
27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue0035.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | No manipulator unitbuf in synopsis 8 |
9 | Nathan Myers 10 | 6 Aug 1998 11 | 12 | 13 |

In , we have a definition for a manipulator 14 | named "unitbuf". Unlike other manipulators, it's not listed 15 | in synopsis. Similarly for "nounitbuf".

16 | 17 | 18 | 19 |

Add to the synopsis for <ios> in , after 20 | the entry for "nouppercase", the prototypes:

21 | 22 |
23 | 
ios_base& unitbuf(ios_base& str);
24 | ios_base& nounitbuf(ios_base& str);
25 |
26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0037.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Leftover "global" reference 8 |
9 | Nathan Myers 10 | 6 Aug 1998 11 | 12 | 13 |

In the overview of locale semantics, paragraph 4, is the sentence

14 | 15 |
16 |

If Facet is not present in a locale (or, failing that, in the global locale), it throws 17 | the standard exception bad_cast.

18 |
19 | 20 |

This is not supported by the definition of use_facet<>, and represents semantics 21 | from an old draft.

22 | 23 | 24 | 25 |

In , paragraph 4, delete the parenthesized 26 | expression

27 | 28 |
29 |

(or, failing that, in the global locale)

30 |
31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue0039.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | istreambuf_iterator<>::operator++(int) definition garbled 8 |
9 | Nathan Myers 10 | 6 Aug 1998 11 | 12 | 13 |

Following the definition of istreambuf_iterator<>::operator++(int) in paragraph 14 | 3, the standard contains three lines of garbage text left over from a previous edit.

15 | 16 |
17 | 
istreambuf_iterator<charT,traits> tmp = *this;
18 | sbuf_->sbumpc();
19 | return(tmp);
20 |
21 | 22 | 23 | 24 |

In , delete the three lines of code at the 25 | end of paragraph 3.

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0040.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Meaningless normative paragraph in examples 8 |
9 | Nathan Myers 10 | 6 Aug 1998 11 | 12 | 13 |

Paragraph 3 of the locale examples is a description of part of an 14 | implementation technique that has lost its referent, and doesn't mean 15 | anything.

16 | 17 | 18 | 19 |

Delete paragraph 3 which begins "This 20 | initialization/identification system depends...", or (at the 21 | editor's option) replace it with a place-holder to keep the paragraph 22 | numbering the same.

23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue0043.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Locale table correction 8 |
9 | Brendan Kehoe 10 | 1 Jun 1998 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /xml/issue0047.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Imbue() and getloc() Returns clauses swapped 8 |
9 | Matt Austern 10 | 21 Jun 1998 11 | 12 | 13 |

Section 27.4.2.3 specifies how imbue() and getloc() work. That 14 | section has two RETURNS clauses, and they make no sense as 15 | stated. They make perfect sense, though, if you swap them. Am I 16 | correct in thinking that paragraphs 2 and 4 just got mixed up by 17 | accident?

18 | 19 | 20 | 21 |

In swap paragraphs 2 and 4.

22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue0048.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Use of non-existent exception constructor 8 |
9 | Matt Austern 10 | 21 Jun 1998 11 | 12 | 13 |

27.4.2.1.1, paragraph 2, says that class failure initializes the 14 | base class, exception, with exception(msg). Class exception (see 15 | 18.6.1) has no such constructor.

16 | 17 | 18 | 19 |

Replace , paragraph 2, with

20 | 21 |
22 |

EFFECTS: Constructs an object of class failure.

23 |
24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0054.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Basic_streambuf's destructor 8 |
9 | Matt Austern 10 | 25 Jun 1998 11 | 12 | 13 |

The class synopsis for basic_streambuf shows a (virtual) 14 | destructor, but the standard doesn't say what that destructor does. My 15 | assumption is that it does nothing, but the standard should say so 16 | explicitly.

17 | 18 | 19 | 20 |

Add after paragraph 2:

21 | 22 |
23 |

virtual  ~basic_streambuf();

24 |

Effects: None.

25 |
26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0056.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Showmanyc's return type 8 |
9 | Matt Austern 10 | 29 Jun 1998 11 | 12 | 13 |

The class summary for basic_streambuf<>, in 27.5.2, says that 14 | showmanyc has return type int. However, 27.5.2.4.3 says that its 15 | return type is streamsize.

16 | 17 | 18 | 19 |

Change showmanyc's return type in the 20 | class summary to streamsize.

21 | 22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0058.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Extracting a char from a wide-oriented stream 8 |
9 | Matt Austern 10 | 1 Jul 1998 11 | 12 | 13 |

27.6.1.2.3 has member functions for extraction of signed char and 14 | unsigned char, both singly and as strings. However, it doesn't say 15 | what it means to extract a char from a 16 | basic_streambuf<charT, Traits>.

17 | 18 |

basic_streambuf, after all, has no members to extract a char, so 19 | basic_istream must somehow convert from charT to signed char or 20 | unsigned char. The standard doesn't say how it is to perform that 21 | conversion.

22 | 23 | 24 | 25 |

The Standard is correct as written. There is no such extractor and 26 | this is the intent of the LWG.

27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0062.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>Sync</tt>'s return value 8 |
9 | Matt Austern 10 | 6 Aug 1998 11 | 12 | 13 |

The Effects clause for sync() (27.6.1.3, paragraph 36) says that it 14 | "calls rdbuf()->pubsync() and, if that function returns -1 15 | ... returns traits::eof()."

16 | 17 |

That looks suspicious, because traits::eof() is of type 18 | traits::int_type while the return type of sync() is int.

19 | 20 | 21 | 22 |

In , paragraph 36, change "returns 23 | traits::eof()" to "returns -1". 24 |

25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0072.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Do_convert phantom member function 8 |
9 | Nathan Myers 10 | 24 Aug 1998 11 | 12 | 13 |

In par 3, and in par 8, a nonexistent member function 14 | "do_convert" is mentioned. This member was replaced with 15 | "do_in" and "do_out", the proper referents in the 16 | contexts above.

17 | 18 | 19 | 20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue0073.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>is_open</tt> should be const 8 |
9 | Matt Austern 10 | 27 Aug 1998 11 | 12 | 13 |

Classes basic_ifstream, basic_ofstream, and 14 | basic_fstream all have a member function is_open. It 15 | should be a const member function, since it does nothing but 16 | call one of basic_filebuf's const member functions.

17 | 18 | 19 | 20 |

Not a defect. This is a deliberate feature; const streams would be 21 | meaningless.

22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0078.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo: event_call_back 8 |
9 | Nico Josuttis 10 | 29 Sep 1998 11 | 12 | 13 |

typo: event_call_back should be event_callback  

14 | 15 | 16 | 17 |

In the synopsis change 18 | "event_call_back" to "event_callback".

19 | 20 | 21 | -------------------------------------------------------------------------------- /xml/issue0080.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Global Operators of complex declared twice 8 |
9 | Nico Josuttis 10 | 29 Sep 1998 11 | 12 | 13 |

Both 26.2.1 and 26.2.2 contain declarations of global operators for 14 | class complex. This redundancy should be removed.

15 | 16 | 17 | 18 |

Reduce redundancy according to the general style of the standard.

19 | 20 | 21 | -------------------------------------------------------------------------------- /xml/issue0082.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Missing constant for set elements 8 |
9 | Nico Josuttis 10 | 29 Sep 1998 11 | 12 | 13 |

Paragraph 5 specifies:

14 | 15 |

16 | For set and multiset the value type is the same as the key type. For 17 | map and multimap it is equal to pair<const Key, T>. 18 |

19 | 20 |

Strictly speaking, this is not correct because for set and multiset 21 | the value type is the same as the constant key type.

22 | 23 | 24 | 25 |

Not a defect. The Standard is correct as written; it uses a 26 | different mechanism (const &) for set and 27 | multiset. See issue for a related 28 | issue.

29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue0085.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | String char types 8 |
9 | Nico Josuttis 10 | 29 Sep 1998 11 | 12 | 13 |

The standard seems not to require that charT is equivalent to 14 | traits::char_type. So, what happens if charT is not equivalent to 15 | traits::char_type?

16 | 17 | 18 | 19 |

There is already wording in paragraph 3 that 20 | requires them to be the same.

21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue0087.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Error in description of string::compare() 6 |
7 | Nico Josuttis 8 | 29 Sep 1998 9 | 10 | 11 |

The following compare() description is obviously a bug:

12 | 13 | 
14 | int compare(size_type pos, size_type n1, 
15 |             charT *s, size_type n2 = npos) const;
16 |
17 | 18 |

because without passing n2 it should compare up to the end of the 19 | string instead of comparing npos characters (which throws an 20 | exception)

21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0088.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Inconsistency between string::insert() and string::append() 6 |
7 | Nico Josuttis 8 | 29 Sep 1998 9 | 10 | 11 |

Why does

12 | 
  template<class InputIterator> 
13 |        basic_string& append(InputIterator first, InputIterator last);
14 | 15 |

return a string, while

16 | 
  template<class InputIterator> 
17 |        void insert(iterator p, InputIterator first, InputIterator last);
18 | 19 |

returns nothing ?

20 | 21 | 22 | 23 |

The LWG believes this stylistic inconsistency is not sufficiently 24 | serious to constitute a defect.

25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0089.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Missing throw specification for string::insert() and string::replace() 6 |
7 | Nico Josuttis 8 | 29 Sep 1998 9 | 10 | 11 |

All insert() and replace() members for strings with an iterator as 12 | first argument lack a throw specification. The throw 13 | specification should probably be: length_error if size exceeds 14 | maximum.

15 | 16 | 17 | 18 |

Considered a duplicate because it will be solved by the resolution 19 | of issue .

20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue0097.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Insert inconsistent definition 8 |
9 | AFNOR 10 | 7 Oct 1998 11 | 12 | 13 |

insert(iterator, const value_type&) is defined both on 14 | sequences and on set, with unrelated semantics: insert here (in 15 | sequences), and insert with hint (in associative containers). They 16 | should have different names (B.S. says: do not abuse overloading).

17 | 18 | 19 | 20 |

This is not a defect in the Standard. It is a genetic misfortune of 21 | the design, for better or for worse.

22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0099.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Reverse_iterator comparisons completely wrong 8 |
9 | AFNOR 10 | 7 Oct 1998 11 | 12 | 13 |

The <, >, <=, >= comparison operator are wrong: they 14 | return the opposite of what they should.

15 | 16 |

Note: same problem in CD2, these were not even defined in CD1. SGI 17 | STL code is correct; this problem is known since the Morristown 18 | meeting but there it was too late

19 | 20 | 21 | 22 |

This is not a defect in the Standard. A careful reading shows the Standard is correct 23 | as written. A review of several implementations show that they implement 24 | exactly what the Standard says.

25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0100.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Insert iterators/ostream_iterators overconstrained 8 |
9 | AFNOR 10 | 7 Oct 1998 11 | 12 | 13 |

Overspecified For an insert iterator it, the expression *it is 14 | required to return a reference to it. This is a simple possible 15 | implementation, but as the SGI STL documentation says, not the only 16 | one, and the user should not assume that this is the case.

17 | 18 | 19 | 20 |

The LWG believes this causes no harm and is not a defect in the 21 | standard. The only example anyone could come up with caused some 22 | incorrect code to work, rather than the other way around.

23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue0102.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Bug in insert range in associative containers 8 |
9 | AFNOR 10 | 7 Oct 1998 11 | 12 | 13 |

Table 69 of Containers say that a.insert(i,j) is linear if [i, j) is ordered. It seems 14 | impossible to implement, as it means that if [i, j) = [x], insert in an associative 15 | container is O(1)!

16 | 17 | 18 | 19 |

N+log (size()) if [i,j) is sorted according to value_comp()

20 | 21 | 22 | 23 |

Subsumed by issue .

24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0104.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Description of basic_string::operator[] is unclear 8 |
9 | AFNOR 10 | 7 Oct 1998 11 | 12 | 13 |

It is not clear that undefined behavior applies when pos == size () 14 | for the non const version.

15 | 16 | 17 | 18 |

Rewrite as: Otherwise, if pos > size () or pos == size () and 19 | the non-const version is used, then the behavior is undefined.

20 | 21 | 22 | 23 |

The Standard is correct. The proposed resolution already appears in 24 | the Standard.

25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0105.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | fstream ctors argument types desired 8 |
9 | AFNOR 10 | 7 Oct 1998 11 | 12 | 13 | 14 | 15 |

fstream ctors take a const char* instead of string.
16 | fstream ctors can't take wchar_t

17 | 18 |

An extension to add a const wchar_t* to fstream would make the 19 | implementation non conforming.

20 | 21 | 22 | 23 |

This is not a defect in the Standard. It might be an 24 | interesting extension for the next Standard.

25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0106.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Numeric library private members are implementation defined 8 |
9 | AFNOR 10 | 7 Oct 1998 11 | 12 | 13 |

This is the only place in the whole standard where the implementation has to document 14 | something private.

15 | 16 | 17 | 18 |

19 | Remove the comment which says "// remainder implementation defined" from: 20 |

21 | 22 |
    23 |
    • 24 |
    • 25 |
    • 26 |
    • 27 |
28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue0124.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | ctype_byname<charT>::do_scan_is & do_scan_not return type should be const charT* 8 |
9 | Judy Ward 10 | 15 Dec 1998 11 | 12 | 13 |

In Section 14 | ctype_byname<charT>::do_scan_is() and do_scan_not() are declared 15 | to return a const char* not a const charT*.

16 | 17 | 18 | 19 |

Change Section do_scan_is() and 20 | do_scan_not() to return a const 21 | charT*.

22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue0125.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | valarray<T>::operator!() return type is inconsistent 8 |
9 | Judy Ward 10 | 15 Dec 1998 11 | 12 | 13 |

In Section valarray<T>::operator!() is 14 | declared to return a valarray<T>, but in Section it is declared to return a valarray<bool>. The 15 | latter appears to be correct.

16 | 17 | 18 | 19 |

Change in Section the declaration of 20 | operator!() so that the return type is 21 | valarray<bool>.

22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0126.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | typos in Effects clause of ctype::do_narrow() 8 |
9 | Judy Ward 10 | 15 Dec 1998 11 | 12 |

Typos in 22.2.1.1.2 need to be fixed.

 13 | 14 | 15 |

In Section change:

16 | 17 | 
   do_widen(do_narrow(c),0) == c
18 | 19 |

to:

20 | 21 | 
   do_widen(do_narrow(c,0)) == c
22 | 23 |

and change:

24 | 25 | 
   (is(M,c) || !ctc.is(M, do_narrow(c),dfault) )
26 | 27 |

to:

28 | 29 | 
   (is(M,c) || !ctc.is(M, do_narrow(c,dfault)) )
30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue0131.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | list::splice throws nothing 8 |
9 | Howard Hinnant 10 | 6 Mar 1999 11 | 12 | 13 |

What happens if a splice operation causes the size() of a list to grow 14 | beyond max_size()?

15 | 16 | 17 | 18 |

Size() cannot grow beyond max_size(). 

19 | 20 | 21 | 22 | -------------------------------------------------------------------------------- /xml/issue0133.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | map missing get_allocator() 8 |
9 | Howard Hinnant 10 | 6 Mar 1999 11 | 12 |

The title says it all.

 13 | 14 | 15 |

Insert in , paragraph 2, 16 | after operator= in the map declaration:

17 | 18 | 
    allocator_type get_allocator() const;
19 | 20 | 21 | -------------------------------------------------------------------------------- /xml/issue0148.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Functions in the example facet BoolNames should be const 8 |
9 | Jeremy Siek 10 | 3 Jun 1999 11 | 12 | 13 |

In paragraph 13, the do_truename() and 14 | do_falsename() functions in the example facet BoolNames should be 15 | const. The functions they are overriding in 16 | numpunct_byname<char> are const.

17 | 18 | 19 | 20 |

In paragraph 13, insert "const" in 21 | two places:

22 |
23 |

string do_truename() const { return "Oui Oui!"; }
24 | string do_falsename() const { return "Mais Non!"; }

25 |
26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0150.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Find_first_of says integer instead of iterator 8 |
9 | Matt McClure 10 | 30 Jun 1999 11 | 12 | 13 | 14 | 15 | 16 |

Change paragraph 2 from:

17 | 18 |
19 |

Returns: The first iterator i in the range [first1, last1) such 20 | that for some integer j in the range [first2, last2) ...

21 |
22 | 23 |

to:

24 | 25 |
26 |

Returns: The first iterator i in the range [first1, last1) such 27 | that for some iterator j in the range [first2, last2) ...

28 |
29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue0152.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo in <tt>scan_is()</tt> semantics 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

The semantics of scan_is() (paragraphs 4 and 6) is not exactly described 14 | because there is no function is() which only takes a character as 15 | argument. Also, in the effects clause (paragraph 3), the semantic is also kept 16 | vague.

17 | 18 | 19 | 20 |

In paragraphs 4 and 6, change the returns 21 | clause from:

22 |
23 |

"... such that is(*p) 24 | would..."

25 |
26 |

to:  "... such that is(m, *p) 27 | would...."

28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue0155.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo in naming the class defining the class <tt>Init</tt> 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

There are conflicting statements about where the class 14 | Init is defined. According to paragraph 2 15 | it is defined as basic_ios::Init, according to it is defined as ios_base::Init.

16 | 17 | 18 | 19 |

Change paragraph 2 from 20 | "basic_ios::Init" to 21 | "ios_base::Init".

22 | 23 | 24 | 25 |

Although not strictly wrong, the standard was misleading enough to warrant 26 | the change.

27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0156.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo in <tt>imbue()</tt> description 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

There is a small discrepancy between the declarations of 14 | imbue(): in the argument is passed as 15 | locale const& (correct), in it 16 | is passed as locale const (wrong).

17 | 18 | 19 | 20 |

In change the imbue argument 21 | from "locale const" to "locale 22 | const&".

23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue0157.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Meaningless error handling for <tt>pword()</tt> and <tt>iword()</tt> 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

According to paragraphs 2 and 4 of , the 14 | functions iword() and pword() "set the 15 | badbit (which might throw an exception)" on 16 | failure. ... but what does it mean for ios_base to set the 17 | badbit? The state facilities of the IOStream library are 18 | defined in basic_ios, a derived class! It would be possible 19 | to attempt a down cast but then it would be necessary to know the 20 | character type used...

21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0159.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Strange use of <tt>underflow()</tt> 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

The description of the meaning of the result of 14 | showmanyc() seems to be rather strange: It uses calls to 15 | underflow(). Using underflow() is strange because 16 | this function only reads the current character but does not extract 17 | it, uflow() would extract the current character. This should 18 | be fixed to use sbumpc() instead.

19 | 20 | 21 | 22 |

Change paragraph 1, 23 | showmanyc()returns clause, by replacing the word 24 | "supplied" with the words "extracted from the 25 | stream".

26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0160.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo: Use of non-existing function <tt>exception()</tt> 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

The paragraph 4 refers to the function exception() which 14 | is not defined. Probably, the referred function is 15 | basic_ios<>::exceptions().

16 | 17 | 18 | 19 |

In , , paragraph 1, 20 | , paragraph 3, and , 21 | paragraph 1, change "exception()" to 22 | "exceptions()".

23 | 24 | Note to Editor: "exceptions" with an "s" 25 | is the correct spelling. 26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0161.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo: <tt>istream_iterator</tt> vs. <tt>istreambuf_iterator</tt> 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

The note in the second paragraph pretends that the first argument 14 | is an object of type istream_iterator. This is wrong: It is 15 | an object of type istreambuf_iterator.

16 | 17 | 18 | 19 |

Change from:

20 |
21 |

The first argument provides an object of the istream_iterator class...

22 |
23 |

to

24 |
25 |

The first argument provides an object of the istreambuf_iterator class...

26 |
27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue0166.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Really "formatted output functions"? 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

From it appears that all the functions 14 | defined in have to construct a 15 | sentry object. Is this really intended?

16 | 17 |

This is basically the same problem as issue but 18 | for output instead of input.

19 | 20 | 21 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue0168.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo: formatted vs. unformatted 8 |
9 | Dietmar Kühl 10 | 20 Jul 1999 11 | 12 | 13 |

The first paragraph begins with a descriptions what has to be done 14 | in formatted output functions. Probably this is a typo and the 15 | paragraph really want to describe unformatted output functions...

16 | 17 | 18 | 19 |

In paragraph 1, the first and last 20 | sentences, change the word "formatted" to 21 | "unformatted":

22 |
23 |

"Each unformatted output function begins ..."
24 | "... value specified for the unformatted output 25 | function."

26 |
27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0174.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo: <tt>OFF_T</tt> vs. <tt>POS_T</tt> 8 |
9 | Dietmar Kühl 10 | 23 Jul 1999 11 | 12 | 13 |

According to paragraph 1 of this section, streampos is the 14 | type OFF_T, the same type as streamoff. However, in 15 | paragraph 6 the streampos gets the type POS_T

16 | 17 | 18 | 19 |

Change paragraph 1 from "typedef 20 | OFF_T streampos;" to "typedef POS_T 21 | streampos;"

22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0176.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>exceptions()</tt> in <tt>ios_base</tt>...? 8 |
9 | Dietmar Kühl 10 | 23 Jul 1999 11 | 12 | 13 |

The "overload" for the function exceptions() in 14 | paragraph 8 gives the impression that there is another function of 15 | this function defined in class ios_base. However, this is not 16 | the case. Thus, it is hard to tell how the semantics (paragraph 9) can 17 | be implemented: "Call the corresponding member function specified 18 | in clause ."

19 | 20 | 21 | 22 |

In paragraph 8, move the declaration of the 23 | function exceptions()into class basic_ios.

24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue0196.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Placement new example has alignment problems 8 |
9 | Herb Sutter 10 | 15 Dec 1998 11 | 12 | 13 |

The example in paragraph 4 reads:

14 | 15 |
16 | 17 |

[Example: This can be useful for constructing an object at a known address:
18 |
19 |    char place[sizeof(Something)];
20 |    Something* p = new (place) Something();
21 |
22 | end example]

23 | 24 |
25 | 26 |

This example has potential alignment problems.

27 | 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue0223.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | reverse algorithm should use iter_swap rather than swap 8 |
9 | Dave Abrahams 10 | 21 Mar 2000 11 | 12 | 13 |

Shouldn't the effects say "applies iter_swap to all pairs..."?

14 | 15 | 16 | 17 |

In , replace:

18 |

19 | Effects: For each non-negative integer i <= (last - first)/2, 20 | applies swap to all pairs of iterators first + i, (last - i) - 1. 21 |

22 |

with:

23 |

24 | Effects: For each non-negative integer i <= (last - first)/2, 25 | applies iter_swap to all pairs of iterators first + i, (last - i) - 1. 26 |

27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0234.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typos in allocator definition 8 |
9 | Dietmar Kühl 10 | 24 Apr 2000 11 | 12 | 13 |

In paragraphs 12 and 13 the effects of construct() and 14 | destruct() are described as returns but the functions actually 15 | return void.

16 | 17 | 18 | 19 |

Substitute "Returns" by "Effect".

20 | 21 | 22 | -------------------------------------------------------------------------------- /xml/issue0237.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Undefined expression in complexity specification 8 |
9 | Dietmar Kühl 10 | 24 Apr 2000 11 | 12 | 13 |

The complexity specification in paragraph 6 says that the complexity 14 | is linear in first - last. Even if operator-() is 15 | defined on iterators this term is in general undefined because it 16 | would have to be last - first.

17 | 18 | 19 | 20 |

Change paragraph 6 from

21 |

Linear in first - last.

22 |

to become

23 |

Linear in distance(first, last).

24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue0256.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | typo in 27.4.4.2, p17: copy_event does not exist 8 |
9 | Martin Sebor 10 | 21 Aug 2000 11 | 12 | 13 |

14 | 27.4.4.2, p17 says 15 |

16 | 17 |

18 | -17- Before copying any parts of rhs, calls each registered callback 19 | pair (fn,index) as (*fn)(erase_event,*this,index). After all parts but 20 | exceptions() have been replaced, calls each callback pair that was 21 | copied from rhs as (*fn)(copy_event,*this,index). 22 |

23 | 24 |

25 | The name copy_event isn't defined anywhere. The intended name was 26 | copyfmt_event. 27 |

28 | 29 | 30 | 31 |

Replace copy_event with copyfmt_event in the named paragraph.

32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue0262.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Bitmask operator ~ specified incorrectly 8 |
9 | Beman Dawes 10 | 03 Sep 2000 11 | 12 | 13 |

14 | The ~ operation should be applied after the cast to int_type. 15 |

16 | 17 | 18 | 19 |

20 | Change 17.3.2.1.2 [lib.bitmask.types] operator~ from: 21 |

22 | 23 | 
24 |    bitmask operator~ ( bitmask X )
25 |      { return static_cast< bitmask>(static_cast<int_type>(~ X)); }
26 |
27 | 28 |

29 | to: 30 |

31 | 32 | 
33 |    bitmask operator~ ( bitmask X )
34 |      { return static_cast< bitmask>(~static_cast<int_type>(X)); }
35 |
36 | 37 | 38 | -------------------------------------------------------------------------------- /xml/issue0268.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo in locale synopsis 8 |
9 | Martin Sebor 10 | 5 Oct 2000 11 | 12 | 13 | 14 |

The synopsis of the class std::locale in 22.1.1 contains two typos: 15 | the semicolons after the declarations of the default ctor 16 | locale::locale() and the copy ctor locale::locale(const locale&) 17 | are missing.

18 | 19 | 20 | 21 |

Add the missing semicolons, i.e., change

22 | 23 | 
24 |     //  construct/copy/destroy:
25 |         locale() throw()
26 |         locale(const locale& other) throw()
27 |
28 | 29 |

in the synopsis in 22.1.1 to

30 | 31 | 
32 |     //  construct/copy/destroy:
33 |         locale() throw();
34 |         locale(const locale& other) throw();
35 |
36 | 37 | 38 | -------------------------------------------------------------------------------- /xml/issue0272.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Missing parentheses around subexpression 8 |
9 | Martin Sebor 10 | 02 Nov 2000 11 | 12 | 13 |

14 | 27.4.4.3, p4 says about the postcondition of the function: If 15 | rdbuf()!=0 then state == rdstate(); otherwise 16 | rdstate()==state|ios_base::badbit. 17 |

18 | 19 |

20 | The expression on the right-hand-side of the operator==() needs to be 21 | parenthesized in order for the whole expression to ever evaluate to 22 | anything but non-zero. 23 |

24 | 25 | 26 | 27 |

28 | Add parentheses like so: rdstate()==(state|ios_base::badbit). 29 |

30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0273.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Missing ios_base qualification on members of a dependent class 8 |
9 | Martin Sebor 10 | 02 Nov 2000 11 | 12 | 13 |

27.5.2.4.2, p4, and 27.8.1.6, p2, 27.8.1.7, p3, 27.8.1.9, p2, 14 | 27.8.1.10, p3 refer to in and/or out w/o ios_base:: qualification. 15 | That's incorrect since the names are members of a dependent base 16 | class (14.6.2 [temp.dep]) and thus not visible.

17 | 18 | 19 | 20 |

Qualify the names with the name of the class of which they are 21 | members, i.e., ios_base.

22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0288.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <cerrno> requirements missing macro EILSEQ 8 |
9 | Judy Ward 10 | 30 Dec 2000 11 | 12 | 13 |

14 | ISO/IEC 9899:1990/Amendment1:1994 Section 4.3 States: "The list 15 | of macros defined in <errno.h> is adjusted to include a new 16 | macro, EILSEQ" 17 |

18 | 19 |

20 | ISO/IEC 14882:1998(E) section 19.3 does not refer 21 | to the above amendment. 22 |

23 | 24 | 25 | 26 | 27 |

28 | Update Table 26 (section 19.3) "Header <cerrno> synopsis" 29 | and Table 95 (section C.2) "Standard Macros" to include EILSEQ. 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue0312.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Table 27 is missing headers 8 |
9 | Martin Sebor 10 | 29 Mar 2001 11 | 12 | 13 |

Table 27 in section 20 lists the header <memory> (only) for 14 | Memory (lib.memory) but neglects to mention the headers 15 | <cstdlib> and <cstring> that are discussed in .

16 | 17 | 18 | 19 |

Add <cstdlib> and <cstring> to Table 27, in the same row 20 | as <memory>.

21 | 22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue0315.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Bad "range" in list::unique complexity 8 |
9 | Andy Sawyer 10 | 1 May 2001 11 | 12 | 13 |

14 | , Para 21 describes the complexity of 15 | list::unique as: "If the range (last - first) is not empty, exactly 16 | (last - first) -1 applications of the corresponding predicate, 17 | otherwise no applications of the predicate)". 18 |

19 | 20 |

21 | "(last - first)" is not a range. 22 |

23 | 24 | 25 | 26 |

27 | Change the "range" from (last - first) to [first, last). 28 |

29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue0321.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo in num_get 8 |
9 | Kevin Djang 10 | 17 May 2001 11 | 12 | 13 |

14 | Section 22.2.2.1.2 at p7 states that "A length specifier is added to 15 | the conversion function, if needed, as indicated in Table 56." 16 | However, Table 56 uses the term "length modifier", not "length 17 | specifier". 18 |

19 | 20 | 21 | 22 |

23 | In 22.2.2.1.2 at p7, change the text "A length specifier is added ..." 24 | to be "A length modifier is added ..." 25 |

26 | 27 | 28 | 29 |

C uses the term "length modifier". We should be consistent.

30 | 31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue0326.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Missing typedef in moneypunct_byname 8 |
9 | Martin Sebor 10 | 05 Jul 2001 11 | 12 | 13 |

The definition of the moneypunct facet contains the typedefs char_type 14 | and string_type. Only one of these names, string_type, is defined in 15 | the derived facet, moneypunct_byname.

16 | 17 | 18 | 19 |

For consistency with the numpunct facet, add a typedef for 20 | char_type to the definition of the moneypunct_byname facet in 21 | .

22 | 23 | 24 | 25 |

The absence of the typedef is irrelevant. Users can still access 26 | the typedef, because it is inherited from the base class.

27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue0328.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Bad sprintf format modifier in money_put<>::do_put() 8 |
9 | Martin Sebor 10 | 07 Jul 2001 11 | 12 | 13 |

The sprintf format string , "%.01f" (that's the digit one), in the 14 | description of the do_put() member functions of the money_put facet in 15 | 22.2.6.2.2, p1 is incorrect. First, the f format specifier is wrong 16 | for values of type long double, and second, the precision of 01 17 | doesn't seem to make sense. What was most likely intended was 18 | "%.0Lf"., that is a precision of zero followed by the L length 19 | modifier.

20 | 21 | 22 | 23 |

Change the format string to "%.0Lf".

24 | 25 | 26 |

Fixes an obvious typo

 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0337.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | replace_copy_if's template parameter should be InputIterator 8 |
9 | Detlef Vollmann 10 | 07 Sep 2001 11 | 12 | 13 |

From c++std-edit-876:

14 | 15 |

16 | In section before p4: The name of the first 17 | parameter of template replace_copy_if should be "InputIterator" 18 | instead of "Iterator". According to p1 the 19 | parameter name conveys real normative meaning. 20 |

21 | 22 | 23 | 24 |

Change Iterator to InputIterator.

25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0345.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | type tm in <cwchar> 8 |
9 | Clark Nelson 10 | 19 Oct 2001 11 | 12 | 13 |

14 | C99, and presumably amendment 1 to C90, specify that <wchar.h> 15 | declares struct tm as an incomplete type. However, table 48 in does not mention the type tm as being declared in 16 | <cwchar>. Is this omission intentional or accidental? 17 |

18 | 19 | 20 | 21 |

In section , add "tm" to table 48.

22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue0349.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Minor typographical error in ostream_iterator 8 |
9 | Andy Sawyer 10 | 24 Oct 2001 11 | 12 | 13 |

24.5.2 [lib.ostream.iterator] states:

14 | 
15 |     [...]
16 | 
17 |     private:
18 |     // basic_ostream<charT,traits>* out_stream; exposition only
19 |     // const char* delim; exposition only
20 |
21 | 22 |

Whilst it's clearly marked "exposition only", I suspect 'delim' 23 | should be of type 'const charT*'.

24 | 25 | 26 | 27 |

28 | In , replace const char* delim with 29 | const charT* delim. 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue0363.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Missing exception specification in 27.4.2.1.1 8 |
9 | Walter Brown and Marc Paterno 10 | 20 May 2002 11 | 12 | 13 |

14 | The destructor of ios_base::failure should have an empty throw 15 | specification, because the destructor of its base class, exception, is 16 | declared in this way. 17 |

18 | 19 | 20 | 21 |

Change the destructor to

22 | 
23 |   virtual ~failure() throw();
24 |
25 | 26 | 27 | 28 |

Fixes an obvious glitch. This is almost editorial.

29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0375.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | basic_ios should be ios_base in 27.7.1.3 8 |
9 | Ray Lischner 10 | 14 Aug 2002 11 | 12 | 13 |

14 | In Section : Table 90, Table 91, and paragraph 15 | 14 all contain references to "basic_ios::" which should be 16 | "ios_base::". 17 |

18 | 19 | 20 | 21 |

22 | Change all references to "basic_ios" in Table 90, Table 91, and 23 | paragraph 14 to "ios_base". 24 |

25 | 26 | 27 |

Fixes an obvious typo.

 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue0377.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | basic_string::insert and length_error 6 |
7 | Ray Lischner 8 | 16 Aug 2002 9 | 10 | 11 |

12 | Section , paragraph 4, contains the following, 13 | "Then throws length_error if size() >= npos - rlen." 14 |

15 | 16 |

17 | Related to DR 83, this sentence should probably be removed. 18 |

19 | 20 | 21 | 22 | 23 | 24 |

This requirement is redundant but correct. No change is 25 | needed.

 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0391.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | non-member functions specified as const 8 |
9 | James Kanze 10 | 10 Dec 2002 11 | 12 | 13 |

14 | The specifications of toupper and tolower both specify the functions as 15 | const, althought they are not member functions, and are not specified as 16 | const in the header file synopsis in section . 17 |

18 | 19 | 20 | 21 |

In , remove const from the function 22 | declarations of std::toupper and std::tolower

23 | 24 | 25 |

Fixes an obvious typo

 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0400.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | redundant type cast in lib.allocator.members 8 |
9 | Markus Mauhart 10 | 27 Feb 2003 11 | 12 | 13 |

14 | allocator members, contains 15 | the following 3 lines: 16 |

17 | 18 | 
19 |   12 Returns: new((void *) p) T( val)
20 |      void destroy(pointer p);
21 |   13 Returns: ((T*) p)->~T()
22 |
23 | 24 |

25 | The type cast "(T*) p" in the last line is redundant cause 26 | we know that std::allocator<T>::pointer is a typedef for T*. 27 |

28 | 29 | 30 | 31 |

32 | Replace "((T*) p)" with "p". 33 |

34 | 35 | 36 |

Just a typo, this is really editorial.

 37 | 38 | 39 | -------------------------------------------------------------------------------- /xml/issue0411.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Wrong names of set member functions 8 |
9 | Daniel Frey 10 | 9 Jul 2003 11 | 12 | 13 |

14 | paragraph 1 reads: 15 | "The semantics of the set operations are generalized to multisets in a 16 | standard way by defining union() to contain the maximum number of 17 | occurrences of every element, intersection() to contain the minimum, and 18 | so on." 19 |

20 | 21 |

22 | This is wrong. The name of the functions are set_union() and 23 | set_intersection(), not union() and intersection(). 24 |

25 | 26 | 27 | 28 |

Change that sentence to use the correct names.

29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0441.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Is fpos::state const? 8 |
9 | Vincent Leloup 10 | 17 Nov 2003 11 | 12 | 13 |

14 | In section fpos<stateT>::state() is declared 15 | non const, but in section it is declared const. 16 |

17 | 18 | 19 | 20 |

21 | In section , change the declaration of 22 | fpos<stateT>::state() to const. 23 |

24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0442.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | sentry::operator bool() inconsistent signature 8 |
9 | Vincent Leloup 10 | 18 Nov 2003 11 | 12 | 13 |

14 | In section paragraph 4, in description part 15 | basic_ostream<charT, traits>::sentry::operator bool() is declared 16 | as non const, but in section 27.6.2.3, in synopsis it is declared 17 | const. 18 |

19 | 20 | 21 | 22 |

23 | In section paragraph 4, change the declaration 24 | of sentry::operator bool() to const. 25 |

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0443.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | filebuf::close() inconsistent use of EOF 8 |
9 | Vincent Leloup 10 | 20 Nov 2003 11 | 12 | 13 |

14 | In section par6, in effects description of 15 | basic_filebuf<charT, traits>::close(), overflow(EOF) is used twice; 16 | should be overflow(traits::eof()). 17 |

18 | 19 | 20 | 21 |

22 | Change overflow(EOF) to overflow(traits::eof()). 23 |

24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0447.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Wrong template argument for time facets 8 |
9 | Pete Becker 10 | 26 Dec 2003 11 | 12 | 13 |

14 | 22.1.1.1.1/4, table 52, "Required Instantiations", lists, among others: 15 |

16 | 
17 |     time_get<char,InputIterator>
18 |     time_get_byname<char,InputIterator>
19 |     time_get<wchar_t,OutputIterator>
20 |     time_get_byname<wchar_t,OutputIterator>
21 |
22 | 23 |

24 | The second argument to the last two should be InputIterator, not 25 | OutputIterator. 26 |

27 | 28 | 29 | 30 |

31 | Change the second template argument to InputIterator. 32 |

33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | -------------------------------------------------------------------------------- /xml/issue0448.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Random Access Iterators over abstract classes 8 |
9 | Dave Abrahams 10 | 7 Jan 2004 11 | 12 | 13 |

14 | Table 76, the random access iterator requirement table, says that the 15 | return type of a[n] must be "convertible to T". When an iterator's 16 | value_type T is an abstract class, nothing is convertible to T. 17 | Surely this isn't an intended restriction? 18 |

19 | 20 | 21 | 22 |

23 | Change the return type to "convertible to T const&". 24 |

25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0450.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | set::find is inconsistent with associative container requirements 8 |
9 | Bill Plauger 10 | 30 Jan 2004 11 | 12 | 13 |

map/multimap have:

14 | 15 | 
16 |     iterator find(const key_type& x) const;
17 |     const_iterator find(const key_type& x) const;
18 |
19 | 20 |

21 | which is consistent with the table of associative container requirements. 22 | But set/multiset have: 23 |

24 | 
25 |     iterator find(const key_type&) const;
26 |
27 | 28 |

29 | set/multiset should look like map/multimap, and honor the requirements 30 | table, in this regard. 31 |

32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | -------------------------------------------------------------------------------- /xml/issue0469.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | vector<bool> ill-formed relational operators 8 |
9 | Martin Sebor 10 | 28 Jun 2004 11 | 12 | 13 |

14 | The overloads of relational operators for vector<bool> specified 15 | in [lib.vector.bool] are redundant (they are semantically identical 16 | to those provided for the vector primary template) and may even be 17 | diagnosed as ill-formed (refer to Daveed Vandevoorde's explanation 18 | in c++std-lib-13647). 19 |

20 | 21 | 22 | 23 | 24 |

25 | Remove all overloads of overloads of relational operators for 26 | vector<bool> from [lib.vector.bool]. 27 |

28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue0472.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Missing "Returns" clause in std::equal_range 8 |
9 | Prateek R Karandikar 10 | 30 Jun 2004 11 | 12 | 13 |

14 | There is no "Returns:" clause for std::equal_range, which returns non-void. 15 |

16 | 17 | 18 | 19 | 20 | 21 | 22 |

Fixed as part of issue .

23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0474.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] 5 | > 6 | 7 | confusing Footnote 297 8 |
9 | Martin Sebor 10 | 1 Jul 2004 11 | 12 | 13 |

14 | I think Footnote 297 is confused. The paragraph it applies to seems 15 | quite clear in that widen() is only called if the object is not a char 16 | stream (i.e., not basic_ostream<char>), so it's irrelevant what the 17 | value of widen(c) is otherwise. 18 |

19 | 20 | 21 | 22 |

23 | I propose to strike the Footnote. 24 |

25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0486.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | min/max CopyConstructible requirement is too strict 8 |
9 | Dave Abrahams 10 | 13 Oct 2004 11 | 12 | 13 |

A straightforward implementation of these algorithms does not need to 14 | copy T.

15 | 16 | 17 | 18 |

drop the the words "and CopyConstructible" from paragraphs 1 and 4

19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue0496.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Illegal use of "T" in vector<bool> 8 |
9 | richard@ex-parrot.com 10 | 10 Feb 2005 11 | 12 | 13 |

14 | In the synopsis of the std::vector<bool> specialisation in , 15 | the non-template assign() function has the signature

16 | 17 | 
18 |   void assign( size_type n, const T& t );
19 |
20 | 21 |

The type, T, is not defined in this context.

22 | 23 | 24 | 25 |

Replace "T" with "value_type".

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0500.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | do_length cannot be implemented correctly 8 |
9 | Krzysztof Żelechowski 10 | 24 May 2005 11 | 12 | 13 |
    14 |
  1. codecvt::do_length is of type int;
    2. 15 |
  2. it is assumed to be sort-of returning from_next - from of type ptrdiff_t;
    3. 16 |
  3. ptrdiff_t cannot be cast to an int without data loss.
    4. 17 |
18 |

19 | Contradiction. 20 |

21 | 22 | 23 | 24 |

25 |

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue0510.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Input_type for bernoulli_distribution 8 |
9 | Walter Brown 10 | 3 Jul 2005 11 | 12 | 13 |

14 | In [tr.rand.dist.bern] the distribution currently requires; 15 |

16 | 
17 | typedef  int  input_type;
18 |
19 | 20 | 21 | 22 |

23 | We believe this is an unfortunate choice, and recommend instead: 24 |

25 | 
26 | typedef  unsigned int  input_type;
27 |
28 | 29 | 30 | Berlin: Moved to NAD. N1932 makes this moot: the input_type template parameter has been 31 | eliminated. 32 | 33 | 34 | 35 | 36 | 37 | -------------------------------------------------------------------------------- /xml/issue0516.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Seeding subtract_with_carry_01 using a generator 8 |
9 | Walter Brown 10 | 3 Jul 2005 11 | 12 | 13 |

14 | Paragraph 6 says: 15 |

16 |

17 | ... obtained by successive invocations of g, ... 18 |

19 |

20 | We recommend instead: 21 |

22 |

23 | ... obtained by taking successive invocations of g mod 2**32, ... 24 |

25 |

26 | as the context seems to require only 32-bit quantities be used here. 27 |

28 | 29 | 30 | 31 |

32 | Berlin: N1932 adopts the proposed resultion: see 26.3.3.4/7. Moved to Ready. 33 |

34 | 35 | 36 | Portland: Subsumed by N2111. 37 | 38 | 39 | 40 | 41 | -------------------------------------------------------------------------------- /xml/issue0519.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Data() undocumented 8 |
9 | Pete Becker 10 | 3 Jul 2005 11 | 12 | 13 |

14 | array<>::data() is present in the class synopsis, but not documented. 15 |

16 | 17 | 18 | 19 |

20 | Add a new section, after 6.2.2.3: 21 |

22 | 
23 | T*       data()
24 | const T* data() const;
25 |
26 |

27 | Returns: elems. 28 |

29 |

30 | Change 6.2.2.4/2 to: 31 |

32 |

33 | In the case where N == 0, begin() == end(). The return value 34 | of data() is unspecified. 35 |

36 | 37 | 38 | 39 | -------------------------------------------------------------------------------- /xml/issue0533.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | typo in 2.2.3.10/1 8 |
9 | Paolo Carlini 10 | 9 Nov 2005 11 | 12 | 13 |

14 | I'm seeing something that looks like a typo. The Return of get_deleter 15 | says: 16 |

17 |

18 | If *this owns a deleter d... 19 |

20 |

21 | but get_deleter is a free function! 22 |

23 | 24 | 25 | 26 |

27 | Therefore, I think should be: 28 |

29 |

30 | If *this p owns a deleter d... 31 |

32 | 33 | 34 | 35 | -------------------------------------------------------------------------------- /xml/issue0549.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Undefined variable in binomial_distribution 8 |
9 | Matt Austern 10 | 10 Jan 2006 11 | 12 | 13 |

14 | Paragraph 1 says that "A binomial distributon random distribution produces 15 | integer values i>0 with p(i) = (n choose i) * p*i * (1-p)^(t-i), where t and 16 | p are the parameters of the distribution. OK, that tells us what t, p, and i 17 | are. What's n? 18 |

19 | 20 | 21 | 22 |

23 | Berlin: Typo: "n" replaced by "t" in N1932: see 26.3.7.2.2/1. 24 |

25 | 26 | 27 | Portland: Subsumed by N2111. 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0555.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [tr1] 8.21/1: typo 6 |
7 | Paolo Carlini 8 | 2 Feb 2006 9 | 10 | 11 |

12 | This one, if nobody noticed it yet, seems really editorial: 13 | s/cstbool/cstdbool/ 14 |

15 | 16 | 17 | 18 |

19 | Change 8.21p1: 20 |

21 |

22 | -1- The header behaves as if it defines the additional macro defined in 23 | <cstdbool> by including the header <cstdbool>. 24 |

25 | 26 | 27 | Redmond: Editorial. 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue0568.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | [tr1] <tt>log2</tt> overloads missing 8 |
9 | Paolo Carlini 10 | 7 Mar 2006 11 | 12 | 13 |

14 | log2 is missing from the list of "additional overloads" in p1. 15 |

16 | 17 |

18 | Hinnant: This is a TR1 issue only. It is fixed in the current (N2135) WD. 19 |

20 | 21 | 22 | Batavia (2009-05): 23 | 24 |

25 | We agree this has been fixed in the Working Draft. 26 | Move to NAD. 27 |

28 | 29 | 30 | 31 |

32 | Add log2 to the list of functions in p1. 33 |

34 | 35 | 36 | 37 | -------------------------------------------------------------------------------- /xml/issue0571.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Update C90 references to C99? 8 |
9 | Beman Dawes 10 | 8 Apr 2006 11 | 12 | 13 |

14 | 1.2 Normative references [intro.refs] of the WP currently refers to ISO/IEC 15 | 9899:1990, Programming languages - C. Should that be changed to ISO/IEC 16 | 9899:1999? 17 |

18 |

19 | What impact does this have on the library? 20 |

21 | 22 | 23 | 24 |

25 | In 1.2/1 [intro.refs] of the WP, change: 26 |

27 |
28 |
    29 |
  • ISO/IEC 9899:19901999 + TC1 + TC2, Programming languages - C
    • 30 |
31 |
32 | 33 | 34 | 35 |

36 | Recommend NAD, fixed editorially. 37 |

38 | 39 | 40 | -------------------------------------------------------------------------------- /xml/issue0584.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | missing int <tt>pow(int,int)</tt> functionality 8 |
9 | Beman Dawes 10 | 15 Jun 2006 11 | 12 | 13 |

14 | There is no pow() function for any integral type. 15 |

16 | 17 | 18 | 19 |

20 | Add something like: 21 |

22 | 23 | 
24 | template< typename T>
25 | T power( T x, int n );
26 | // requires: n >=0
27 |
28 | 29 | 30 |

31 | Toronto: We already have double pow(integral, integral) from p11. 32 |

33 | 34 | 35 | -------------------------------------------------------------------------------- /xml/issue0616.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | missing 'typename' in ctype_byname 8 |
9 | Bo Persson 10 | 16 Dec 2006 11 | 12 | 13 |

14 | Section 22.2.1.2 defines the ctype_byname class template. It contains the 15 | line 16 |

17 | 18 | 
19 | typedef ctype<charT>::mask   mask;
20 |
21 | 22 | 23 | 24 | 25 |

26 | as this is a dependent type, it should obviously be 27 |

28 | 29 | 
30 | typedef typename ctype<charT>::mask   mask;
31 |
32 | 33 | 34 | 35 | -------------------------------------------------------------------------------- /xml/issue0636.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | 26.5.2.3 valarray::operator[] 8 |
9 | Bo Persson 10 | 11 Feb 2007 11 | 12 | 13 |

14 | The signature of the const operator[] has been changed to return a const 15 | reference. 16 |

17 |

18 | The description in paragraph 1 still says that the operator returns by 19 | value. 20 |

21 | 22 | Pete recommends editorial fix. 23 | 24 | 25 | 26 | 27 |

28 |

29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0641.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Editorial fix for 27.6.4 (N2134) 8 |
9 | Daniel Krügler 10 | 18 Feb 2007 11 | 12 | 13 |

14 | The function f in para 4 () references an unknown strm 15 | in the following line: 16 |

17 | 18 | 
19 | mg.get(Iter(str.rdbuf()), Iter(), intl, strm, err, mon);
20 |
21 | 22 | 23 | 24 |

25 | Change , p4: 26 |

27 | 28 | 
29 | mg.get(Iter(str.rdbuf()), Iter(), intl, strm, err, mon);
30 |
31 | 32 | 33 | Oxford: Editorial. 34 | 35 | 36 | 37 | 38 | 39 | -------------------------------------------------------------------------------- /xml/issue0646.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | const incorrect match_result members 8 |
9 | Daniel Krügler 10 | 26 Feb 2007 11 | 12 | 13 |

14 | (root and para 3) in N2134 defines the two function template 15 | members format as non-const functions, although they are declared 16 | as const in /3. 17 |

18 | 19 | 20 | 21 |

22 | Add the missing const specifier to both format overloads described 23 | in section . 24 |

25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue0656.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Typo in subtract_with_carry_engine declaration 8 |
9 | Daniel Krügler 10 | 8 Mar 2007 11 | 12 | 13 |

14 | the header <random> synopsis 15 | contains an unreasonable closing curly brace inside the 16 | subtract_with_carry_engine declaration. 17 |

18 | 19 | 20 | 21 |

22 | Change the current declaration in 23 |

24 | 25 | 
26 | template <class UIntType, size_t w}, size_t s, size_t r>
27 | class subtract_with_carry_engine;
28 |
29 | 30 | 31 | 32 | Pete: Recommends editorial. 33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue0702.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | [tr1] Restriction in associated Legendre functions 8 |
9 | Christopher Crawford 10 | 30 Jun 2007 11 | 12 | 13 |

14 | One other small thing, in , the restriction should be 15 | |x| <= 1, not x >= 0.

16 | 17 | 18 | Batavia (2009-05): 19 | 20 |
21 |

22 | The error has been corrected in the pending IS. 23 |

24 |

25 | Move to NAD. 26 |

27 |
28 | 29 | 30 | 31 |

32 |

33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue0703.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>map::at()</tt> need a complexity specification 8 |
9 | Joe Gottman 10 | 3 Jul 2007 11 | 12 | 13 |

14 | map::at() need a complexity specification. 15 |

16 | 17 | 18 | 19 |

20 | Add the following to the specification of map::at(), : 21 |

22 |
23 |

24 | Complexity: logarithmic. 25 |

26 |
27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue0722.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Missing [c.math] functions <tt>nanf</tt> and <tt>nanl</tt> 8 |
9 | Daniel Krügler 10 | 27 Aug 2007 11 | 12 | 13 |

14 | In the listing of , table 108: Header <cmath> synopsis I miss 15 | the following C99 functions (from 7.12.11.2): 16 |

17 | 18 | 
19 | float nanf(const char *tagp);
20 | long double nanl(const char *tagp);
21 |
22 | 23 |

24 | (Note: These functions cannot be overloaded and they are also not 25 | listed anywhere else) 26 |

27 | 28 | 29 | 30 |

31 | In , table 108, section "Functions", add nanf and nanl 32 | just after the existing entry nan. 33 |

34 | 35 | 36 | 37 | -------------------------------------------------------------------------------- /xml/issue0738.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Editorial issue in [rand.adapt.disc]/3 8 |
9 | Stephan Tolksdorf 10 | 21 Sep 2007 11 | 12 | 13 |

14 | Since the template parameter p and r are of type size_t, the member n in the class 15 | exposition should have type size_t, too. 16 |

17 | 18 | 19 | 20 |

21 | See N2424 22 | for the proposed resolution. 23 |

24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue0779.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Resolution of #283 incomplete 8 |
9 | Daniel Krügler 10 | 25 Jan 2008 11 | 12 | 13 |

14 | The resolution of did not resolve similar necessary changes for algorithm 15 | remove_copy[_if], which seems to be an oversight. 16 |

17 | 18 | 19 | 20 |

21 | In p.6, replace the N2461 requires clause with: 22 |

23 | 24 |

25 | Requires: Type T is EqualityComparable (31). The ranges [first,last) 26 | and [result,result + (last - first)) shall not overlap. The expression *result = *first shall be 27 | valid. 28 |

29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue0790.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>xor_combine::seed</tt> not specified 8 |
9 | P.J. Plauger 10 | 9 Feb 2008 11 | 12 | 13 |

14 | xor_combine::seed(result_type) and seed(seed_seq&) don't say what 15 | happens to each of the sub-engine seeds. (Should probably do the same 16 | to both, unlike TR1.) 17 |

18 | 19 | 20 | Bellevue: 21 | 22 | 23 |

24 | Overcome by the previous proposal. NAD mooted by resolution of . 25 |

26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue0792.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>piecewise_constant_distribution</tt> is undefined for a range with just one endpoint 8 |
9 | P.J. Plauger 10 | 9 Feb 2008 11 | 12 | 13 |

14 | piecewise_constant_distribution is undefined for a range with just one 15 | endpoint. (Probably should be the same as an empty range.) 16 |

17 | 18 | 19 | 20 |

21 | Change paragraph 3b: 22 |

23 | 24 |

25 | b) If firstB == lastB or the sequence w has the length zero, 26 |

27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue0795.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>general_pdf_distribution</tt> should be dropped 8 |
9 | P.J. Plauger 10 | 9 Feb 2008 11 | 12 | 13 |

14 | general_pdf_distribution should be dropped. (It's a research topic in 15 | adaptive numerical integration.) 16 |

17 | 18 | 19 | Stephan Tolksdorf notes: 20 | 21 | 22 |

23 | This appears to be a duplicate of . 24 |

25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue0807.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>tuple</tt> construction should not fail unless its element's construction fails 8 |
9 | Howard Hinnant 10 | 13 Mar 2008 11 | 12 | 13 |

14 | Added a throws clause to bind constructors. I believe the same throws clause 15 | should be added to tuple except it ought to take into account move constructors as well. 16 |

17 | 18 | 19 | 20 |

21 | Add to : 22 |

23 | 24 |
25 |

26 | For each tuple constructor and assignment operator, an exception is thrown only if the construction 27 | or assignment of one of the types in Types throws an exception. 28 |

29 |
30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue0852.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | unordered containers <tt>begin(n)</tt> mistakenly <tt>const</tt> 8 |
9 | Robert Klarer 10 | 12 Jun 2008 11 | 12 | 13 |

14 | In 3 of the four unordered containers the local begin member is mistakenly declared const: 15 |

16 | 17 | 
18 | local_iterator begin(size_type n) const;
19 |
20 | 21 | 22 | 23 |

24 | Change the synopsis in , , and : 25 |

26 | 27 | 
28 | local_iterator begin(size_type n) const;
29 |
30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue0895.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | "Requires:" on std::string::at et al 8 |
9 | James Dennett 10 | 16 Sep 2008 11 | 12 | 13 |

14 | Per discussion, we need an issue open to cover looking at "Requires" 15 | clauses which are not constraints on user code, such as that on 16 | std::basic_string::at. 17 |

18 | 19 | 20 | 2009-07 Frankfurt 21 | 22 | 23 |

24 | Alan to address in paper. 25 |

26 | 27 | 28 | 29 | 30 |

31 |

32 | 33 | 34 | 35 | -------------------------------------------------------------------------------- /xml/issue0969.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | What happened to Library Issue 475? 8 |
9 | Stephan T. Lavavej 10 | 12 Jan 2009 11 | 12 | 13 |

14 | Library Issue has CD1 status, but the non-normative note in 15 | N2723 16 | was removed in 17 | N2798 18 | ( in both drafts). 19 |

20 | 21 | 22 | Batavia (2009-05): 23 | 24 |

25 | Move to NAD Editorial. 26 |

27 | 28 | 29 | 30 |

31 | Restore the non-normative note. It might need to be expressed in terms of concepts. 32 |

33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue0995.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Operational Semantics Unclear 8 |
9 | David Abrahams 10 | 6 Mar 2009 11 | 12 | 13 |

14 | As a practical matter there's disagreement on the meaning of operational 15 | semantics. If the text in p4 isn't 16 | clear, it should be clarified. However, it's not clear whether the 17 | disagreement is merely due to people not being aware of the text. 18 |

19 | 20 | 21 | Batavia (2009-05): 22 | 23 |

24 | Agree with the recommended NAD resolution. 25 |

26 | 27 | 28 | 29 |

30 | Recommend NAD. The text in is 31 | perfectly clear. 32 |

33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue1007.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>throw_with_nested</tt> not concept enabled 8 |
9 | Alisdair Meredith 10 | 11 Mar 2009 11 | 12 | 13 | 14 |

Addresses JP 29

15 | 16 |

17 | throw_with_nested does not use concept. 18 |

19 | 20 | 21 | Summit: 22 | 23 | 24 |

25 | Agreed. 26 |

27 | 28 | 29 | 30 | 31 | 32 |

33 | Alisdair initially proposed wording in 34 | N2619. 35 |

36 |

37 | We are awaiting an updated paper based on feedback from the San Francisco 38 | review. 39 |

40 | 41 | 42 | 43 | -------------------------------------------------------------------------------- /xml/issue1060.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Embedded nulls in NTBS 8 |
9 | Alisdair Meredith 10 | 13 Mar 2009 11 | 12 | 13 | 14 |

15 | Definition of null-terminated sequences allow for embedded nulls. This is 16 | surprising, and probably not supportable with the intended use cases. 17 |

18 | 19 | 20 | Batavia (2009-05): 21 | 22 |

23 | We agree with the issue, but believe this can be handled editorially. 24 | Move to NAD Editorial. 25 |

26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue1061.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Bad indexing for tuple access to pair (Editorial?) 8 |
9 | Alisdair Meredith 10 | 13 Mar 2009 11 | 12 | 13 | 14 |

15 | The definition of get implies that get must return the second element if 16 | given a negative integer. 17 |

18 | 19 | 20 | Batavia (2009-05): 21 | 22 |

23 | Move to NAD Editorial. 24 |

25 | 26 | 27 | 28 | 29 |

30 | p5: 31 |

32 | 33 | 
34 | template<int size_t I, class T1, class T2> 
35 |   requires True<(I < 2)> 
36 |   const P& get(const pair<T1, T2>&);
37 |
38 |
39 | 40 | 41 | 42 | 43 | -------------------------------------------------------------------------------- /xml/issue1073.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Declaration of <tt>allocator_arg</tt> should be <tt>constexpr</tt> 8 |
9 | Alisdair Meredith 10 | 19 Mar 2009 11 | 12 | 13 | 14 |

15 | Declaration of allocator_arg should be constexpr to ensure constant 16 | initialization. 17 |

18 | 19 | 20 | Batavia (2009-05): 21 | 22 |

23 | We agree with the proposed resolution. Move to Tentatively Ready. 24 |

25 | 26 | 27 | 28 |

29 | Change p2: 30 |

31 | 32 | 
33 | // 20.8.1, allocator argument tag
34 | struct allocator_arg_t { };
35 | constexpr allocator_arg_t allocator_arg = allocator_arg_t();
36 |
37 | 38 | 39 | 40 | 41 | -------------------------------------------------------------------------------- /xml/issue1081.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>basic_string</tt> needs to be a concept-constrained template 8 |
9 | Howard Hinnant 10 | 22 Mar 2009 11 | 12 | 13 |

Addresses UK 216, JP 46, JP 48 [CD1]

14 | 15 |

16 | All the containers use concepts for their iterator usage, exect for 17 | basic_string. This needs fixing. 18 |

19 | 20 |

21 | Use concepts for iterator template parameters throughout the chapter. 22 |

23 | 24 | 25 | Summit: 26 | 27 |

28 | NB comments to be handled by Dave Abrahams and Howard Hinnant with 29 | advice from PJP: UK216 (which duplicates) JP46, JP48. JP46 supplies 30 | extensive proposed wording; start there. 31 |

32 | 33 | 34 | 35 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /xml/issue1082.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>codecvt</tt> needs to be a concept-constrained template 8 |
9 | Howard Hinnant 10 | 22 Mar 2009 11 | 12 | 13 |

Addresses JP 49 [CD1]

14 | 15 |

16 | codecvt does not use concept. For example, create CodeConvert 17 | concept and change as follows. 18 |

19 | 20 | 
21 | template<CodeConvert Codecvt, class Elem = wchar_t>
22 |   class wstring_convert {
23 |
24 | 25 | 26 | Summit: 27 | 28 |

29 | To be handled by Howard Hinnant, Dave Abrahams, Martin Sebor, PJ Plauger. 30 |

31 | 32 | 33 | 34 | 35 | 36 | 37 | -------------------------------------------------------------------------------- /xml/issue1083.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>InputIterator</tt> and <tt>OutputIterator</tt> template parameters need to be concept constraints 8 |
9 | Howard Hinnant 10 | 22 Mar 2009 11 | 12 | 13 |

Addresses JP 52, JP 53 [CD1]

14 | 15 |

16 | InputIterator does not use concept. 17 |

18 | 19 |

20 | OutputIterator does not use concept. 21 |

22 | 23 |

24 | Comments include proposed wording. 25 |

26 | 27 | 28 | Summit: 29 | 30 |

31 | To be handled by Howard Hinnant, Dave Abrahams, Martin Sebor, PJ Plauger. 32 |

33 | 34 | 35 | 36 | 37 | 38 | 39 | -------------------------------------------------------------------------------- /xml/issue1086.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Stream iterators need to be concept-constrained templates 8 |
9 | Howard Hinnant 10 | 22 Mar 2009 11 | 12 | 13 |

Addresses UK 284 [CD1]

14 | 15 |

16 | The stream iterators need constraining with concepts/requrires clauses. 17 |

18 | 19 | 20 | Summit: 21 | 22 |

23 | We agree. To be handled by Howard, Martin and PJ. 24 |

25 | 26 | 27 | 28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue1096.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | unconstrained rvalue ref parameters 8 |
9 | David Abrahams 10 | 21 Mar 2009 11 | 12 | 13 |

14 | TODO: Look at all cases of unconstrained rvalue ref parameters and check 15 | that concept req'ts work when T deduced as reference. 16 |

17 | 18 |

19 | We found some instances where that was not done correctly and we figure 20 | the possibility of deducing T to be an lvalue reference was probably 21 | overlooked elsewhere. 22 |

23 | 24 | 25 | Batavia (2009-05): 26 | 27 |

28 | Move to Open, pending proposed wording from Dave for further review. 29 |

30 | 31 | 32 | 33 |

34 |

35 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /xml/issue1139.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Thread support library not concept enabled 8 |
9 | LWG 10 | 15 Jun 2009 11 | 12 | 13 | 14 |

Addresses US 93, JP 79, UK 333, JP 81

15 | 16 |

17 | The thread chapter is not concept enabled. 18 |

19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue1140.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Numerics library not concept enabled 8 |
9 | LWG 10 | 15 Jun 2009 11 | 12 | 13 | 14 |

Addresses US 84

15 | 16 |

17 | The numerics chapter is not concept enabled. 18 |

19 | 20 |

21 | The portion of this comment dealing with random numbers was resolved by 22 | N2836, 23 | which was accepted in Summit. 24 |

25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue1141.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Input/Output library not concept enabled 8 |
9 | LWG 10 | 15 Jun 2009 11 | 12 | 13 | 14 |

Addresses US 85, JP 67, JP 68, JP 69, JP 72, UK 308

15 | 16 |

17 | The input/output chapter is not concept enabled. 18 |

19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue1142.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Regular expressions library not concept enabled 8 |
9 | LWG 10 | 15 Jun 2009 11 | 12 | 13 | 14 |

Addresses US 86, UK 309, UK 310

15 | 16 |

17 | The regular expressions chapter is not concept enabled. 18 |

19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue1143.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Atomic operations library not concept enabled 8 |
9 | LWG 10 | 15 Jun 2009 11 | 12 | 13 | 14 |

Addresses US 87, UK 311

15 | 16 |

17 | The atomics chapter is not concept enabled. 18 |

19 | 20 |

21 | Needs to also consider issues and . 22 |

23 | 24 | 25 | 2009-10 Santa Cruz: 26 | 27 | 28 |

29 | NAD EditorialResolved. Addressed by 30 | N2992. 31 |

32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | -------------------------------------------------------------------------------- /xml/issue1216.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | LWG 1066 Incomplete? 8 |
9 | Pete Becker 10 | 25 Sep 2009 11 | 12 | 13 |

14 | LWG adds [[noreturn]] to a bunch of things. 15 | It doesn't add it to rethrow_nested(), which seems like an obvious 16 | candidate. I've made the changes indicated in the issue, and haven't 17 | changed rethrow_nested(). 18 |

19 | 20 | 21 | 2009 Santa Cruz: 22 | 23 | 24 |

25 | Move to Ready. 26 |

27 | 28 | 29 | 30 | 31 |

32 | Add [[noreturn]] to rethrow_nested() in . 34 |

35 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /xml/issue1331.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | incorporate move special member functions into library 8 |
9 | Martin Sebor 10 | 10 Mar 2010 11 | 12 | 13 |

14 | Review the library portion of the spec and incorporate the newly added 15 | core feature Move Special Member Functions (N3044). 16 |

17 | 18 |

19 | 2010 Batavia: This has now been done to a large extent. 20 |

21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue1350.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Implicit contructors accidentally made some library types move-only 8 |
9 | Switzerland 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses CH-15

14 |

15 | Due to the new rules about implicit copy and move 16 | constructors some library facilities are now move-only. 17 |

18 | 19 | 20 | Resolution proposed by ballot comment 21 | 22 |

23 | Make them copyable again. 24 |

25 | 26 | 27 | 28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue1351.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Replace dynamic exception specifications with <tt>noexcept</tt> 8 |
9 | Switzerland 10 | 25 Aug 2010 11 | 12 | 13 | 14 |

Addresses CH-16

15 |

16 | Dynamic exception specifications are deprecated. 17 | Deprecated features shouldn't be used in the Standard. 18 |

19 | 20 | 21 | Resolution proposed by ballot comment 22 | 23 |

24 | Replace dynamic exception specifications with noexcept. 25 |

26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue1352.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Apply <tt>noexcept</tt> where library specification says "Throws: Nothing" 8 |
9 | Switzerland 10 | 25 Aug 2010 11 | 12 | 13 | 14 |

Addresses CH-17

15 |

16 | The introduction of noexcept makes "Throws: Nothing" clauses looking strange. 17 |

18 | 19 | 20 | Resolution proposed by ballot comment 21 | 22 |

23 | Consider replacing "Throws: Nothing." clause by 24 | the respective noexcept specification. 25 |

26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue1384.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Function <tt>pack_arguments</tt> is poorly named 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-98

14 |

15 | pack_arguments is poorly named. It does not reflect the 16 | fact that it is a tuple creation function and that it forwards 17 | arguments. 18 |

19 | 20 | 21 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 22 | 23 | 24 | 25 | 26 |

27 | Rename pack_arguments to forward_as_tuple throughout the standard. 28 |

29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue1390.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Limit speculative compilation for constructible/convertible traits 8 |
9 | DIN 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses DE-17

14 |

15 | Speculative compilation for std::is_constructible and 16 | std::is_convertible should be limited, similar to the core 17 | language (see 14.8.2 paragraph 8). 18 |

19 | 20 | 21 | 2010-10-24 Daniel adds: 22 | 23 | 24 |

25 | Accepting n3142 would solve this issue. 26 |

27 | 28 | 29 | 30 |

31 | Resolved by paper n3142. 32 |

33 | 34 | 35 | -------------------------------------------------------------------------------- /xml/issue1394.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>is_constructible</tt> reports false positives 8 |
9 | DIN 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses DE-19

14 |

15 | The fundamental trait is_constructible reports false 16 | positives, e.g. 17 |

18 | 
19 | is_constructible<char*, void*>::value
20 |
21 |

22 | evaluates to true, even though a corresponding variable initialization would be ill-formed. 23 |

24 | 25 | Resolved in Rapperswil by paper N3047. 26 | 27 | 28 | 29 | 30 |

31 | Remove all false positives from the domain of is_constructible. 32 |

33 | 34 | 35 | -------------------------------------------------------------------------------- /xml/issue1395.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Inconsistent reference links should be unified 8 |
9 | Japan 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses JP-32

14 |

15 | Representations of reference link are not unified. 16 | Most reference links to clause (table) number, say X, are 17 | in the form "Clause X" ("Table X") capitalized, and 18 | subsection Y.Y.Y is referenced with its number only in the 19 | form "Y.Y.Y". Whether they are parenthesized or not 20 | depends on the context. 21 | However there are some notations "(Z)" consisting of only 22 | a number Z in parentheses to confer Clause or Table 23 | number Z. 24 |

25 | 26 | 27 | 28 |

29 | Change "(10)" to "(Clause 10)". 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue1400.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | FCD <tt>function</tt> does not need an <tt>explicit</tt> default constructor 8 |
9 | Japan 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses JP-4

14 |

15 | Really does the function require that default constructor is explicit? 16 |

17 | 18 | 19 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 20 | 21 | 22 | 23 | 24 | 25 |

Remove explicit.

26 | 
27 | function();
28 | template <class A>
29 | function(allocator_arg_t, const A& a);
30 |
31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue1405.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Move <tt>scoped_allocator_adaptor</tt> into separate header 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-107

14 |

15 | scoped_allocator_adaptor should have its own header. 16 |

17 | 18 | 19 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 20 | 21 | 22 | 23 | 24 |

25 | See Appendix 1 - Additional Details 26 |

27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue1407.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Synch <tt>shared_ptr</tt> constructors taking movable types 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-108

14 | 15 |

16 | shared_ptr should have the same policy for constructing 17 | from auto_ptr as unique_ptr. Currently it does not. 18 |

19 | 20 | 21 | Resolved in Rapperswil by paper N3109. 22 | 23 | 24 | 25 | 26 | 27 |

28 | Add 29 | 

30 | template <class Y> explicit shared_ptr(auto_ptr<Y>&); 
31 |

32 | to [util.smartptr.shared.const] (and to the synopsis). 33 |

34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue1411.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Add a compile-time flag to detect <tt>monotonic_clock</tt> 8 |
9 | DIN 10 | 25 Aug 2010 11 | 12 | 13 | 14 |

Addresses DE-20

15 |

16 | The library component monotonic_clock is conditionally 17 | supported, but no compile-time flag exists that allows 18 | user-code to query its existence. Further-on there exist no 19 | portable means to simulate such a query. (To do so, user 20 | code would be required to add types to namespace 21 | std::chrono.) 22 |

23 | 24 | 25 | 26 |

27 | Provide a compile-time flag (preferably a macro) 28 | that can be used to query the existence of 29 | monotonic_clock. 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue1415.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Iterator stability bans the short-string optimization 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

14 | Requirements on iterators swapping allegiance would 15 | disallow the small-string optimization. 16 |

17 | 18 | Resolved in Rapperswil by paper N3108. 19 | 20 | 21 | 22 | 23 | 24 |

25 | Add an exclusion for basic_string to the sentence 26 | beginning “Every iterator referring to an 27 | element...”. Add a sentence to 21.4.6.8/2 saying 28 | that iterators and references to string elements 29 | remain valid, but it is not specified whether they 30 | refer to the same string or the other string. 31 |

32 | 33 | 34 | 35 | -------------------------------------------------------------------------------- /xml/issue1417.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>front/back</tt> on a zero-sized <tt>array</tt> should be undefined 8 |
9 | BSI 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses GB-112

14 | 15 |

16 | Should the effect of calling front/back on a zero-sized 17 | array really be implementation defined i.e. require the 18 | implementor to define behaviour? 19 |

20 | 21 | 22 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 23 | 24 | 25 | 26 | 27 |

28 | Change "implementation defined" to "undefined" 29 |

30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue1419.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>forward_list::erase_after</tt> should return an iterator 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-117

14 |

15 | forward_list::erase_after should return an iterator. 16 |

17 | 18 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 19 | 20 | 21 | 22 | 23 | 24 |

25 | See Appendix 1 - Additional Details 26 |

27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue1425.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>set</tt> constructor accepting an allocator as a single parameter should be explicit 8 |
9 | Japan 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses JP-8

14 | 15 |

16 | Constructor accepting an allocator as a single parameter 17 | should be qualified as explicit. 18 |

19 | 20 | 21 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 22 | 23 | 24 | 25 | 26 | 27 |

Add explicit.

28 | 
29 | namespace std {
30 | template <class Key, class Compare = less<Key>,
31 | class Allocator = allocator<Key> >
32 | class set {
33 | public:
34 | ...
35 | explicit set(const Allocator&);
36 |
37 | 38 | 39 | 40 | -------------------------------------------------------------------------------- /xml/issue1431.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>is_permutation</tt> must be more restrictive 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-120

14 | 15 |

16 | is_permutation is underspecified for anything but the 17 | simple case where both ranges have the same value type 18 | and the comparison function is an equivalence relation. 19 |

20 | 21 | 22 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 23 | 24 | 25 | 26 | 27 |

28 | Restrict is_permutation to the case where it is well 29 | specified. See Appendix 1 - Additional Details 30 |

31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue1433.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>random_shuffle</tt> and <tt>shuffle</tt> should have consistent signatures 8 |
9 | BSI 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses GB-119

14 |

15 | The functions random_shuffle and shuffle both take 16 | arguments providing a source of randomness, but one 17 | take its argument by rvalue reference, and the other 18 | requires an lvalue reference. The technical merits of which 19 | form of argument passing should be settled for this 20 | specific case, and a single preferred form used 21 | consistently. 22 |

23 | 24 | 25 | 26 |

27 | [DEPENDS ON WHETHER RVALUE OR 28 | LVALUE REFERENCE IS THE PREFERRED 29 | FORM] 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue1434.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | For <tt>min/max</tt> functions replace variadic arguments by <tt>initializer_list</tt> argument 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-122

14 |

15 | It was the LWG's intent in Pittsburgh that N2772 be applied to the WP. 16 |

17 | 18 | Resolved in Rapperswil by paper N3106. 19 | 20 | 21 | 22 | 23 | 24 |

Apply N2772 to the WP.

25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue1441.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Floating-point test functions are incorrectly specified 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-136

14 | 15 |

16 | Floating-point test functions are incorrectly specified. 17 |

18 | 19 | 20 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 21 | 22 | 23 | 24 | 25 | 26 |

See Appendix 1 - Additional Details

27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue1444.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>OFF_T</tt> is not defined 8 |
9 | BSI 10 | 25 Aug 2010 11 | 12 | 13 | 14 |

Addresses GB-123

15 |

16 | Several rows in table 124 specify a Return type of 17 | 'OFF_T', which does not appear to be a type defined in 18 | this standard. 19 |

20 | 21 | 22 | 23 |

24 | Resolve outstanding references to the removed type 'OFF_T'. 25 |

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue1451.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>regex</tt> should support allocators 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 | 14 |

Addresses US-141

15 | 16 |

17 | std::basic_regex should have an allocator for all the 18 | reasons that a std::string does. For example, I can use 19 | boost::interprocess to put a string or vector 20 | in shared memory, but not a regex. 21 |

22 | 23 | 24 | 25 |

26 | Add allocators to regexes; see paper N3171 27 | in the pre-Batavia mailing. 28 |

29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue1463.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Inconsistent value assignment for <tt>atomic_bool</tt> 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 | 14 |

Addresses US-157

15 | 16 |

17 | atomic_bool has a volatile assignment operator but not a 18 | non-volatile operator. The other integral types have both. 19 |

20 | 21 | 22 | 23 |

24 | Add a non-volatile assignment operator to atomic_bool. 25 |

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue1470.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | "Same-ness" curiosities 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-165

14 | 15 |

16 | According to p. 23: 17 |

18 |

19 | “is the same that same as that of” is not grammatical (and is not clear) 20 |

21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue1476.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Meaningless specification of spurious failure 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 | 14 |

Addresses US-177

15 | 16 |

17 | The first sentence of this paragraph doesn't make sense. 18 |

19 | 20 | 21 | Resolution proposed in ballot comment 22 | 23 |

24 | Figure out what it's supposed to say, and say it. 25 |

26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue1483.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>__STDCPP_THREADS spelling</tt> 8 |
9 | DIN 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses DE-23

14 | 15 |

16 | Predefined macros usually start and end with two 17 | underscores, see 16.8 and FDIS 29124 = WG21 N3060 18 | clause 7. __STDCPP_THREADS should blend in. 19 |

20 | 21 | 22 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 23 | 24 | 25 | 26 | 27 | 28 |

29 | Change the macro name to __STDCPP_THREADS__. 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue1495.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Condition variable <tt>wait_for</tt> return value insufficient 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-191

14 | 15 |

16 | The condition variable wait_for returning cv_status is insufficient. 17 |

18 | 19 | 20 | Resolution proposed by ballot comment: 21 | 22 |

23 | Return a duration of timeout remaining instead. 24 | See Appendix 1 of n3141 - Additional Details, p. 211 25 |

26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue1500.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Consider removal of <tt>native_handle()</tt> 8 |
9 | Switzerland 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses CH-32

14 | 15 |

16 | Given that the lock type can be something the underlying 17 | doesn't know 'native_handle()' is probably 18 | unimplementable on essentially all platforms. 19 |

20 | 21 | 22 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 23 | 24 | 25 | 26 | 27 | 28 |

29 | Consider the removal of 'native_handle()'. 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue1506.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>set_exception</tt> with a null pointer 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-198

14 |

15 | promise::set_exception can be called with a null pointer, 16 | but none of the descriptions of the get() functions for the 17 | three types of futures say what happens for this case. 18 |

19 | 20 | Resolved in Rapperswil by a motion to directly apply the words from the ballot comment in N3102. 21 | 22 | 23 | 24 | 25 | 26 |

27 | Add the following sentence to the end of 28 | 30.6.5/22: The behavior of a program that calls 29 | set_exception with a null pointer is undefined. 30 |

31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue1509.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | No restriction on calling <tt>future::get</tt> more than once 8 |
9 | INCITS 10 | 25 Aug 2010 11 | 12 | 13 |

Addresses US-202

14 |

15 | The note in this paragraph says "unlike future, calling get 16 | more than once on the same atomic_future object is well 17 | defined and produces the result again." There is nothing 18 | in future that says anything negative about calling get 19 | more than once. 20 |

21 | 22 | 23 | Resolution proposed by ballot comment: 24 | 25 |

26 | Remove this note, or add words to the 27 | requirements for future that reflect what this note 28 | says. 29 |

30 | 31 | 32 | 33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue1523.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>noexcept</tt> for Clause 29 8 |
9 | Hans Boehm 10 | 13 Nov 2010 11 | 12 | 13 |

Addresses GB-63 for Clause 29

14 | 15 |

Clause 29 does not specify noexcept for any of the atomic operations. 16 | It probably should, though that's not completely clear. 17 | In particular, atomics may want to throw in implementations that support transactional memory. 18 |

19 | 20 | 21 | 22 |

23 | Apply paper N3251, 24 | noexcept for the Atomics Library. 25 |

26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue2237.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt><cuchar></tt> macros 8 |
9 | Jason Merrill 10 | 29 Jan 2013 11 | 4 12 | 13 | 14 |

15 | Apparently C1X changes __STDC_UTF_16__ and __STDC_UTF_32__ from macros 16 | defined in uchar.h (and reflected in C++ by Table 79) to be predefined by the compiler. 17 | Do we want to do the same? 18 |

19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue2248.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | <tt>numeric_limits::is_iec559</tt> misnamed 8 |
9 | Pete Becker 10 | 8 Mar 2013 11 | 4 12 | 13 | 14 | 15 |

16 | This member should probably be named "is_ieee754". Or at least the standard should explain that IEC-559 no longer exists, 17 | and that it's been superseded by IEEE-754. 18 |

19 | 20 | 2016-06, Oulu 21 |

The ISO version of the standard is ISO/IEC/IEEE 60559:2011, 22 | which C11 Annex F refers to as IEC 60559 23 | (although C still refers to it as IEC 559 in the __STDC_IEC_559__ macro). 24 |

25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue2249.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [CD] Remove <tt>gets</tt> from <tt><cstdio></tt> 6 |
7 | Jonathan Wakely 8 | 17 Apr 2013 9 | 10 | 11 |

Addresses GB 9

12 | 13 |

14 | In the current C++ standard claims that <cstdio> defines a 15 | function called "gets" but it has no declaration or semantics, because it was removed from C11, 16 | having been deprecated since C99. We should remove it for C++14. 17 |

18 | 19 | 2013-09 Chicago 20 |

21 | Will resolve with the wording in the NB comment. 22 |

23 | 24 | 25 | 26 | 27 | 28 |

Resolved by resolution as suggested by NB comment GB 9

29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue2352.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | ] > 5 | 6 | 7 | Is a default-constructed <tt>std::seed_seq</tt> intended to produce a predictable <tt>.generate()</tt>? 8 |
9 | Thomas Plum 10 | 2 Dec 2013 11 | 2 12 | 13 | 14 |

15 | With respect to class seed_seq , is a default-constructed 16 | std::seed_seq intended to produce a predictable .generate() sequence? 17 |

18 | Implementations differ. 19 |

20 | 21 | 2014-02-10 22 |

Priority set to 2

23 | 24 | 2022-08-24 Status changed: New → NAD. 25 |

26 | Discussed in LWG telecon. 27 | The default constructor effects are clear. Implementations agree. 28 |

29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue2478.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Unclear how <tt>wstring_convert</tt> uses <tt>cvtstate</tt> 6 |
7 | Jonathan Wakely 8 | 4 Mar 2015 9 | 4 10 | 11 | 12 |

13 | How do wstring_convert::from_bytes and wstring_convert::to_bytes use 14 | the cvtstate member? 15 |

16 | Is it passed to the codecvt member functions? Is a copy of it passed 17 | to the member functions? "Otherwise it shall be left unchanged" 18 | implies a copy is used, but if that's really what's intended there are 19 | simpler ways to say so. 20 |

21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue2479.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Unclear how <tt>wbuffer_convert</tt> uses <tt>cvtstate</tt> 6 |
7 | Jonathan Wakely 8 | 4 Mar 2015 9 | 4 10 | 11 | 12 |

13 | How does wbuffer_convert use the cvtstate member? 14 |

15 | Is the same conversion state object used for converting both the get 16 | and put areas? That means a read which runs out of bytes halfway 17 | through a multibyte character will leave some shift state in cvtstate, 18 | which would then be used by a following write, even though the shift 19 | state of the get area is unrelated to the put area. 20 |

21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue2480.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Error handling of <tt>wbuffer_convert</tt> unclear 6 |
7 | Jonathan Wakely 8 | 4 Mar 2015 9 | 4 10 | 11 | 12 |

13 | If a codecvt conversion returns codecvt_base::error should that be 14 | treated as EOF? An exception? Should all the successfully converted 15 | characters before a conversion error be available to the users of the 16 | wbuffer_convert and/or the internal streambuf, or does a conversion 17 | error lose information? 18 |

19 | 20 | 21 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue2490.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | <tt><regex></tt> needs lots of <tt>noexcept</tt> 6 |
7 | Stephan T. Lavavej 8 | 27 Mar 2015 9 | 3 10 | 11 | 12 |

13 | Only 4 functions are marked noexcept in all of Clause 28. Many more need to be marked — for example, 14 | regex_error::code(), basic_regex::swap(), and sub_match::length(). 15 |

16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /xml/issue2493.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | <tt>initializer_list</tt> supports incomplete classes 6 |
7 | David Krauss 8 | 27 Apr 2015 9 | 4 10 | 11 | 12 |

13 | The typical use-case of std::initializer_list<T> is for a pass-by-value parameter of T's constructor. 14 | However, this contravenes /2.5 because initializer_list doesn't specifically allow 15 | incomplete types (as do for example std::unique_ptr (/5) and 16 | std::enable_shared_from_this (/2)). 17 |

18 | A resolution would be to copy-paste the relevant text from such a paragraph. 19 |

20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue2502.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | <tt>std::function</tt> does not use <tt>allocator::construct</tt> 6 |
7 | David Krauss 8 | 20 May 2015 9 | 3 10 | 11 | 12 |

13 | It is impossible for std::function to construct its target object using the construct method of a type-erased 14 | allocator. More confusingly, it is possible when the allocator and the target are created at the same time. The means 15 | of target construction should be specified. 16 |

17 | 18 | 2016-08 Chicago 19 |

Tues PM: Resolved by P0302R1.

20 | 21 | 22 | 23 |

24 | Resolved by P0302R1. 25 |

26 | 27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue2508.xml: -------------------------------------------------------------------------------- 1 | 2 | 4 | 5 | ] > 6 | 7 | 8 | §[new.delete.dataraces] wording needs to be updated 9 |
10 | Hans Boehm 11 | 9 Jun 2015 12 | 3 13 | 14 | 15 |

16 | uses obsolete wording. 17 |

18 | It should introduce a "synchronizes with" relationship. "Happens before" is too weak, since that may not composes 19 | with sequenced before. 20 |

21 | The "shall not introduce a data race" wording is probably not technically correct either. These may race with other 22 | (non-allocation/deallocation) concurrent accesses to the object being allocated or deallocated. 23 |

24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue2541.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [parallel.ts] Headers for <tt>ExecutionPolicy</tt> algorithm overloads 6 |
7 | Tim Song 8 | 26 Sep 2015 9 | 1 10 | 11 | 12 |

Addresses: parallel.ts

13 |

14 | provides parallel algorithm overloads for many algorithms in the standard library, 15 | but I can't find any normative wording specifying which headers these new overloads live in. Presumably, if the original 16 | algorithm is in <meow>, the new overloads should be in <experimental/meow>. 17 |

18 | 19 | 2017-11 Albuquerque Saturday issues processing 20 |

Resolved by P0776R1.

21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue2601.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [filesys.ts] [PDTS] Make namespaces consistent with Library TS policy 6 |
7 | FI-5, US-5, GB-3, CH-6 8 | 20 Jan 2014 9 | 10 | 11 |

Addresses: filesys.ts

12 |

The PDTS used a placeholder namespace "tbs" since the Standard Library policy for 13 | TS namespaces had not yet been fully articulated. 14 |

15 | 16 | 2014-02-11 Issaquah: Project editor to make indicated changes to WP, 17 | post notice on lib and SG3 reflectors. 18 | 19 | 20 | 21 | 22 | 23 |

[2014-02-07: Beman Dawes]

24 |

Throughout the WP, change namespace "tbs" to "experimental" as described in the 25 | Library Fundamentals TS working paper, 1.3 Namespaces and headers [general.namespaces]. 26 |

27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue2617.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [filesys.ts] [PDTS] <tt>path</tt> member <tt>swap()</tt> unnecessary 6 |
7 | CH-12 8 | 20 Jan 2014 9 | 10 | 11 |

Addresses: filesys.ts

12 |

As we have move semantics, member swap functions shouldn't be necessary any more.

13 | 14 | 2014-02-12 LWG/SG-3 Issaquah 15 |

No consensus for change. STL pointed out that swap should be noexcept and will submit a separate issue. 16 | 17 | 18 | 19 | 20 |

Remove swap().

21 | 22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue2626.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [filesys.ts] [PDTS] Equivalence is a volatile property 6 |
7 | CH-16 8 | 20 Jan 2014 9 | 10 | 11 |

Addresses: filesys.ts

12 |

Equivalence is a volatile property.

13 | 14 |

Consider adding a note that equivalence cannot be determined race-free.

15 | 16 | 2014-02-13 LWG/SG-3 Issaquah: No consensus for change. Section 2.1 description of races is sufficient. 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /xml/issue2639.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [filesys.ts] [PDTS] <tt>permissions()</tt> is missing from synopsis 6 |
7 | P.J. Plauger 8 | 30 Jan 2014 9 | 10 | 11 |

Addresses: filesys.ts

12 |

permissions function is missing from the summary list.

13 | 14 | 15 | 16 |

17 | [2014-02-07: Beman Dawes comments: Fixed as Editorial.] 18 |

19 | 20 | 21 | 22 | -------------------------------------------------------------------------------- /xml/issue2643.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [filesys.ts] [PDTS] <tt>path::compare(const string&)</tt> should be <tt>path::compare(const string_type&)</tt> 6 |
7 | P.J. Plauger 8 | 30 Jan 2014 9 | 10 | 11 |

Addresses: filesys.ts

12 |

13 | path::compare(const string&) should be path::compare(const string_type&). 14 |

15 | 16 | 2014-02-08 Daniel comments 17 | 18 |

19 | This issue is a duplicate of . The suggested wording of that issue would resolve this issue here as well. 20 |

21 | 22 | 2014-02-13 LWG/SG-3 Issaquah: Agrees with Daniel. 23 | 24 | 25 | 26 | 27 |

28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue2662.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | [filesys.ts] Allocator requirements unspecified 6 |
7 | Daniel Krügler 8 | 19 May 2014 9 | 10 | 11 |

Addresses: filesys.ts

12 |

13 | The SG3 WP refers in several places to a template parameter named "Allocator" but 14 | does not impose requirements on this type. 15 |

16 | 17 | 18 | 19 |

Add the following to 5 Requirements [fs.req]:

20 | 21 |
22 |

23 | Template parameters named Allocator shall meet the C++ Standard's 24 | library Allocator requirements (C++11 §17.6.3.5)

25 |
26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue2675.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | <tt>register_callback</tt> can fail 6 |
7 | David Krauss 8 | 14 Mar 2016 9 | 3 10 | 11 | 12 |

13 | register_callback allocates memory and so it can fail, but the case is unspecified. libc++ sets 14 | badbit, which is consistent with iword and pword. libstdc++ throws std::bad_alloc. 15 |

16 | 17 | 2019-06-13; Billy comments 18 |

19 | Just as an additional data point: MSVC++ agrees with libstdc++ and also throws std::bad_alloc. 20 |

21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue2683.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | <code>filesystem::copy()</code> says "no effects" 6 |
7 | Jonathan Wakely 8 | 19 Apr 2016 9 | 3 10 | 11 | 12 |

In /8 the final bullet says "Otherwise, no effects" which 13 | implies there is no call to ec.clear() if nothing happens, nor any 14 | error condition, is that right? 15 |

16 | 17 | 2016-06 Oulu 18 |

Moved to P0/Ready during issues prioritization.

19 |

Friday: status to Immediate

20 | 21 | 22 | 23 |

Change /8 as indicated:

24 |
Otherwise no effects. For the signature with argument ec, ec.clear(). 25 |
26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue2684.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | priority_queue lacking comparator typedef 6 |
7 | Robert Haberlach 8 | 2 May 2016 9 | 0 10 | 11 | 12 |

The containers that take a comparison functor (set, multiset, 13 | map, and multimap) have a typedef for the comparison functor. 14 | priority_queue does not. 15 |

16 | 17 | 18 | 19 |

Augment [priority.queue] as indicated:

20 | 21 |

22 | 

23 |  typedef Container container_type;
24 |  typedef Compare value_compare;
25 |
26 |

27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue2848.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Pass-through threshold for pool allocator 6 |
7 | Jens Maurer 8 | 15 Dec 2016 9 | 3 10 | 11 | 12 |

13 | p3 talks about a "pass-through-threshold". 14 |

15 | First, the phrase is not defined and it seems it could be easily avoided given the context. 16 |

17 | Second, given the phrasing here, it seems the implementation is essentially allowed to 18 | ignore the value largest_required_pool_block as it sees fit. It is unclear whether 19 | that is the intention. 20 |

21 | 22 | 2017-01-27 Telecon 23 |

Priority 3; Jonathan will ask Alisdair for wording.

24 | 25 | 26 | 27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue2862.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | LWG 2756 should be accepted 6 |
7 | Finland 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 |

Addresses FI 10

13 | 14 |

Adopt the proposed resolution of LWG into C++17, to provide converting constructors and 15 | assignment operators for optional.

16 | 17 |

18 | Proposed change: 19 |

20 |

21 | Adopt the latest proposed resolution of LWG , which should be available by Issaquah. 22 |

23 | 24 | 25 | 26 |

27 | Resolved by resolving LWG . 28 |

29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue2863.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Undo <tt>default_order</tt> changes of maps and sets 6 |
7 | Finland 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 |

Addresses FI 18

13 | 14 |

It was thought that using default_order as the default comparison for maps and sets was not 15 | abi-breaking but this is apparently not the case.

16 | 17 |

18 | Proposed change: 19 |

20 |

21 | Revert the change to the default comparison of maps and sets. 22 |

23 | 24 | 2016-10 Issaquah 25 |

STL and AM want to revert whole paper.

26 | 27 | 2017-03-12, post-Kona 28 |

Resolved reverting P0181R1.

29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /xml/issue2864.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Merge <tt>shared_ptr</tt> changes from Library Fundamentals to C++17 6 |
7 | Finland 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 |

Addresses FI 19

13 | 14 |

The changes in the paper P0414 should be adopted into C++17.

15 | 16 |

17 | Proposed change: 18 |

19 |

20 | Adopt the changes in P0414. 21 |

22 | 23 |

Resolved by the adoption of P0414 in Issaquah

24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue2865.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Resolve all open Library issues for C++17 6 |
7 | Finland 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 |

Addresses FI 2

13 | 14 |

All open Library Issues should be resolved.

15 | 16 |

17 | Proposed change: 18 |

19 |

20 | As LWG sees fit. 21 |

22 | 23 | 2017-03-12, post-Kona 24 |

Closing as NAD; this issue was opened by an over-zealous LWG chair.

25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue2877.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Strengthen meaning of "<em>empty</em> <tt>shared_ptr<T></tt>" in <tt>dynamic_pointer_cast</tt> 6 |
7 | United States 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 |

Addresses US 137

13 | 14 |

Paragraph (6.2): It is intuitive, but not specified, that the empty pointer 15 | returned by a dynamic_pointer_cast should point to null.

16 | 17 |

18 | Proposed change: 19 |

20 |

21 | Rephrase as: 22 |

23 |

24 | Otherwise, shared_ptr<T>(). 25 |

26 | 27 | 28 | 29 |

Resolved by P0414R2, which was adopted in Issaquah.

30 | 31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /xml/issue2879.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Removing C dependencies from signal handler wording 6 |
7 | Canada 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 | 13 | Addresses CA 1 14 |

P0270R1 went through SG1 and LWG but was too late to make it to the straw polls.

15 |

The problems it addresses stem from referring to C11, which came into C++17 at the last minute.

16 |

P0270R1 should have made it in with the C11 change.

17 | 18 |

Proposed change: Apply all of P0270R1, "Removing C dependencies from signal handler wording", to C++17.

19 | 20 | Kona 2017-03-04 21 |

P0270R1 was adopted in Kona

22 | 23 | 24 | 25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue2880.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Relax complexity specifications for non-sequenced policies 6 |
7 | Switzerland 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 | Addresses CH 10 13 | 14 |

Parallel implementations of algorithms may be faster if not restricted to the complexity specifications of serial implementations.

15 |

Proposed change: Add a relaxation of complexity specifications for non-sequenced policies.

16 | 17 | 18 | 19 |

Resolved by the adoption of P0523r1 in Kona 20 |

21 | 22 | 23 | 24 | -------------------------------------------------------------------------------- /xml/issue2881.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Adopt section III of P0308R0 6 |
7 | Switzerland 8 | 3 Feb 2017 9 | 3 10 | 11 | 12 | Addresses CH 7 13 | 14 |

Consider making the variant statically !valueless_by_exception() for cases where is_nothrow_move_constructible_v<T_i> for all alternative types Ti

15 |

Proposed change: Adopt section III of P0308R0.

16 | 17 | 2017-07 Toronto Thurs Issue Prioritization 18 |

Priority 3. This is similar to , Casey to investigate

19 | 20 | 21 | 22 |

23 |

24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue2884.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Relational operators for containers should sfinae; if the underlying type is not comparable, neither should the container be 6 |
7 | Finland 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 | Addresses FI 16 13 | 14 |

Relational operators for containers should sfinae; if the underlying type is not comparable, neither should the container be. Same applies to tuple and pair.

15 | 16 |

Proposed change: Make the relational operators of containers and utility components reflect the validity of the underlying 17 | element types.

18 | 19 | 20 | 2017-06-27 Moved to LEWG after 5 positive votes on c++std-lib. 21 | 22 | 23 | 24 | 25 |

26 |

27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue2924.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | An <tt>ExecutionPolicy</tt> overload for <tt>inner_product()</tt> seems impractical 6 |
7 | United States 8 | 3 Feb 2017 9 | 99 10 | 11 | 12 | Addresses US 184 13 | 14 |

An ExecutionPolicy overload for inner_product() is specified in the synopsis of <numeric>. 15 | Such an overload seems impractical. inner_product() is ordered and cannot be parallelized; this was the motivation for the introduction of transform_reduce().

16 | 17 |

Proposed change: Delete the ExecutionPolicy overload for inner_product().

18 | 19 | 2017-03-12, post-Kona 20 |

Resolved by P0623R0.

21 | 22 | 23 | 24 |

25 |

26 | 27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /xml/issue3189.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Missing requirement for <tt>std::priority_queue</tt> 6 |
7 | Jonathan Wakely 8 | 21 Feb 2019 9 | 3 10 | 11 | 12 |

13 | We don't require that the Compare template parameter can be invoked with arguments of the queue's value type. 14 | It seems like something we can use Mandates: for, since it'll be ill-formed otherwise. Something like 15 | is_invocable_r_v<bool, Compare&, value_type&, value_type&>. 16 |

17 | This might also apply to the Compare parameter for the merge and sort functions of 18 | forward_list and list. 19 |

20 | 21 | 2019-03-05 Priority set to 3 after reflector discussion 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue3309.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Is <tt><ios></tt> implicitly <tt>#include</tt>d by <tt><sstream></tt>, <tt><fstream></tt> etc.? 6 |
7 | Jens Maurer 8 | 01 Nov 2019 9 | 3 10 | 11 | 12 |

13 | It is unclear whether the streams headers implicitly #include <ios> and make (for example) 14 | the name std::basic_ios available after including <sstream>. 15 |

16 | This question becomes more important as header units arrive with modules, where there is an explicit 17 | choice whether to re-export names from subordinate headers. 18 |

19 | 20 | 2019-11 Priority to 3 during Monday issue prioritization in Belfast 21 | 22 | 23 | 24 | 25 | 26 | -------------------------------------------------------------------------------- /xml/issue3401.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Is "as if by" equivalent to "equivalent to"? 6 |
7 | Casey Carter 8 | 14 Feb 2020 9 | 3 10 | 11 | 12 |

13 | We have quite a few occurrences of the phrase "as if by" in Effects: elements in the 14 | library specification. Is the meaning of this phrase the same as "equivalent to"? If so, we 15 | should replace occurrences of "as if by" with "equivalent to" to make it clear that the magic 16 | "Effects: Equivalent to" wording in para 4 17 | is intended to apply. 18 |

19 | 20 | 2020-03-11 Issue Prioritization 21 |

Priority to 3 after reflector discussion.

22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue3497.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Postconditions for <tt>basic_syncbuf::emit()</tt> 6 |
7 | Jonathan Wakely 8 | 10 Nov 2020 9 | 3 10 | 11 | 12 |

13 | p2 says: 14 |

15 |

16 | Postconditions: On success, the associated output is empty. 17 |

18 |

19 | Are there any postconditions on failure? If part of the associated output was written, is that 20 | part still in the associated output? Will another call to emit() duplicate that part? 21 |

22 | 23 | 2020-11-21; Reflector prioritization 24 |

25 | Set priority to 3 during reflector discussions. 26 |

27 | 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /xml/issue3653.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | <tt><coroutine></tt> is freestanding, but uses <tt>std::hash</tt> which is not 6 |
7 | Jonathan Wakely 8 | 17 Dec 2021 9 | 3 10 | 11 | 12 |

13 | The <coroutine> header is required for freestanding implementations, but it defines a 14 | specialization of std::hash, which is not required for freestanding implementations. 15 |

16 | Presumably we should make the std::hash specialization conditionally present. 17 |

18 | 19 | 2022-01-30; Reflector poll 20 |

21 | Set priority to 3 after reflector poll. 22 | Would be resolved by for C++23, 23 | but it's still a defect in C++20. 24 |

25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue3669.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | <tt>std::filesystem</tt> operations should be observable behaviour 6 |
7 | Jens Maurer 8 | 03 Feb 2022 9 | 3 10 | 11 | 12 |

13 | p6.2 should be amended to say that 14 | filesystem operations such as mkdir are observable behaviour. 15 | Any resolution would need CWG review. 16 |

17 | 18 | 2022-03-04; Reflector poll 19 |

20 | Set priority to 3 after reflector poll. 21 |

22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /xml/issue3716.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | §[iterator.concept.forward][forward.iterators] Two different definitions of multi-pass guarantee 6 |
7 | Jiang An 8 | 15 Jun 2022 9 | 3 10 | 11 | 12 |

13 | There are two different definitions of multi-pass guarantee since . The old one (perhaps 14 | introduced by ) seems less reasonable because it requires increment on rvalue iterators of 15 | class types, and the semantics of such increment is largely unspecified. 16 |

17 | Perhaps only the new definition should be used. 18 |

19 | 20 | 2022-07-06; Reflector poll 21 |

22 | Set priority to 3 after reflector poll. 23 |

24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/issue3808.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Inconsistent feature test macros for ranges algorithms 6 |
7 | Daniel Marshall 8 | 02 Nov 2022 9 | 99 10 | 11 | 12 |

13 | ranges::shift is seemingly the only ranges algorithm that incremented the value of an existing feature test macro. 14 |

15 | From what I can tell the only other one that could have done that but didn't is __cpp_lib_starts_ends_with. 16 |

17 | Should there have been a __cpp_lib_ranges_shift or should have __cpp_lib_starts_ends_with incremented 18 | its value when the ranges algorithms were added? 19 |

20 | Kona 2022-11-12 Status changed: New → NAD. 21 | 22 | 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /xml/issue4068.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Terminology for objects whose types model a concept 6 |
7 | 8 | 9 |
10 | Jonathan Wakely 11 | 19 Apr 2024 12 | 99 13 | 14 | 15 |

16 | During review the suggestion was raised that it might 17 | be helpful to be able to talk about "an object that models `Concept`" 18 | instead of "an object whose type models `Concept`" or other more verbose forms. 19 |

20 | 21 | 22 | 23 |

24 |

25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /xml/issue4075.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Thread stability requirement on constructors and destructors 6 |
7 | Detlef Vollmann 8 | 21 Apr 2024 9 | 3 10 | 11 | 12 |

13 | had a requirement for constructors and destructors of 14 | concurrent queue value types to return on the same thread where it was called. 15 |

16 | During the discussion in Tokyo, SG1 decided this to be a general 17 | issue and not specific to concurrent queues. 18 |

19 | 20 | 21 | 2024-06-24; Reflector poll 22 |

23 | Set priority to 3 after reflector poll. Send to SG1. 24 |

25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xml/issue4145.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Unclear how [res.on.data.races] apply to templated functions 6 |
7 | Tim Song 8 | 22 Aug 2024 9 | 3 10 | 11 | 12 |

13 | It's unclear how applies to templated functions that 14 | invoke user-supplied operations. In particular, there's no way to meet those requirements 15 | when a user-supplied operation can perform arbitrary operations. 16 |

17 | Perhaps we need to exclude the invocation of such operations from the scope of the requirements. 18 |

19 | 20 | 2024-10-02; Reflector poll 21 |

22 | Set priority to 3 after reflector poll. 23 |

24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /xml/lwg-template.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Your Title 6 |
7 | Your name 8 | 29 Feb 1900 9 | 99 10 | 11 | 12 |

13 |

14 | 15 | 16 | 17 |

18 |

19 | 20 | 21 | 22 | --------------------------------------------------------------------------------